From 56b3c0cea5d7ff956052bb2a3f4f87c8e3552d3d Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Sun, 29 Aug 2021 01:19:52 +0000 Subject: [PATCH] Update content of files --- .../api/end-to-end/video-calls.html | 215 -- data/core.telegram.org/api/pfs.html | 138 -- .../api/scheduled-messages.html | 156 -- data/core.telegram.org/api/search.html | 179 -- .../api/url-authorization.html | 130 - data/core.telegram.org/bots/inline.html | 182 -- data/core.telegram.org/bots/webhooks.html | 827 ------- .../constructor/account.tmpPassword | 152 -- .../constructor/account.wallPapersNotModified | 132 -- .../constructor/accountDaysTTL.html | 147 -- .../constructor/auth.sentCodeTypeCall | 147 -- .../botInlineMessageMediaVenue.html | 182 -- ...channelAdminLogEventActionEditMessage.html | 152 -- ...elAdminLogEventActionParticipantLeave.html | 132 -- ...nnelAdminLogEventActionToggleSlowMode.html | 155 -- .../constructor/channelParticipantBanned.html | 175 -- .../channelParticipantsBanned.html | 147 -- .../constructor/channels.channelParticipant | 152 -- .../constructor/chatEmpty.html | 147 -- .../constructor/chatParticipants.html | 157 -- .../constructor/contacts.contacts | 157 -- .../constructor/contacts.found | 162 -- .../constructor/contacts.topPeersDisabled | 132 -- .../constructor/contacts.topPeersNotModified | 132 -- .../constructor/disabledFeature.html | 163 -- .../constructor/documentEmpty.html | 147 -- .../constructor/emojiKeyword.html | 152 -- .../constructor/encryptedChatDiscarded.html | 147 -- .../constructor/encryptedFileEmpty.html | 132 -- .../constructor/exportedMessageLink.html | 152 -- .../constructor/fileLocation.html | 182 -- .../help.passportConfigNotModified | 132 -- .../help.termsOfServiceUpdateEmpty | 150 -- .../constructor/inputAppEvent.html | 162 -- .../inputBotInlineResultDocument.html | 179 -- .../constructor/inputBotInlineResultGame.html | 157 -- .../inputEncryptedFileUploaded.html | 162 -- .../inputMediaDocumentExternal.html | 157 -- .../constructor/inputMessagesFilterEmpty.html | 132 -- .../constructor/inputPeerEmpty.html | 132 -- ...nputPrivacyValueAllowChatParticipants.html | 147 -- .../inputPrivacyValueAllowUsers.html | 147 -- .../inputReportReasonGeoIrrelevant.html | 132 -- .../constructor/inputReportReasonOther.html | 147 -- .../constructor/inputUserFromMessage.html | 160 -- .../constructor/inputWallPaperSlug.html | 147 -- .../constructor/inputWebDocument.html | 165 -- .../inputWebFileGeoPointLocation.html | 172 -- .../constructor/inputWebFileLocation.html | 152 -- .../constructor/jsonNull.html | 132 -- .../constructor/jsonObject.html | 147 -- .../constructor/keyboardButtonGame.html | 147 -- .../messageActionCustomAction.html | 147 -- .../constructor/messageActionGameScore.html | 152 -- .../constructor/messageEntityBotCommand.html | 152 -- .../constructor/messageFwdHeader.html | 187 -- .../constructor/messageMediaPhoto.html | 157 -- .../constructor/messageMediaUnsupported.html | 132 -- .../constructor/messages.chats | 147 -- .../constructor/messages.messageEditData | 152 -- .../constructor/messages.messageViews | 157 -- .../constructor/messages.sentEncryptedMessage | 147 -- .../messages.stickerSetInstallResultArchive | 147 -- .../constructor/notifyUsers.html | 132 -- .../constructor/pageBlockAnchor.html | 147 -- .../constructor/pageBlockOrderedList.html | 147 -- .../constructor/pageBlockSubtitle.html | 147 -- .../phoneCallDiscardReasonMissed.html | 132 -- .../constructor/phoneCallProtocol.html | 179 -- .../constructor/phoneConnectionWebrtc.html | 187 -- .../constructor/photoEmpty.html | 147 -- .../constructor/photos.photos | 152 -- .../constructor/pollAnswer.html | 155 -- .../constructor/secureValueErrorFiles.html | 168 -- .../secureValueErrorFrontSide.html | 166 -- .../secureValueTypeIdentityCard.html | 132 -- .../secureValueTypeRentalAgreement.html | 132 -- .../sendMessageGamePlayAction.html | 132 -- .../sendMessageUploadDocumentAction.html | 147 -- .../constructor/statsGraphAsync.html | 152 -- .../constructor/storage.fileMp4 | 132 -- .../constructor/storage.filePartial | 132 -- .../constructor/textItalic.html | 147 -- .../constructor/textMarked.html | 147 -- .../constructor/topPeerCategoryBotsPM.html | 132 -- .../constructor/updateChannelUserTyping.html | 172 -- .../constructor/updateChatParticipants.html | 147 -- .../constructor/updateDeleteMessages.html | 160 -- .../constructor/updateEditChannelMessage.html | 162 -- .../constructor/updateEncryption.html | 152 -- .../constructor/updateGeoLiveViewed.html | 152 -- .../updateReadFeaturedStickers.html | 132 -- .../updateServiceNotification.html | 183 -- .../constructor/updateUserTyping.html | 155 -- .../constructor/updates.differenceSlice | 175 -- .../constructor/upload.fileCdnRedirect | 169 -- .../constructor/userForeign.html | 177 -- .../constructor/userFull.html | 229 -- .../constructor/userStatusOffline.html | 147 -- .../core.telegram.org/constructor/vector.html | 134 -- .../method/account.deleteSecureValue | 153 -- .../method/account.getAccountTTL | 134 -- .../method/account.getNotifySettings | 166 -- .../method/account.resendPasswordEmail | 138 -- .../method/account.setPrivacy | 176 -- .../method/account.updatePasswordSettings | 202 -- .../method/account.updateUsername | 182 -- .../method/account.verifyPhone | 181 -- data/core.telegram.org/method/auth.checkPhone | 176 -- .../method/auth.importLoginToken | 172 -- .../method/channels.getGroupsForDiscussion | 144 -- .../method/channels.togglePreHistoryHidden | 202 -- .../method/contacts.resetTopPeerRating | 175 -- .../method/folders.deleteFolder | 158 -- .../method/langpack.getLanguage | 154 -- .../method/messages.acceptUrlAuth | 174 -- .../method/messages.addChatUser | 227 -- .../method/messages.deleteHistory | 201 -- .../method/messages.editMessage | 323 --- .../method/messages.exportChatInvite | 188 -- .../method/messages.getAllStickers | 153 -- .../method/messages.getDialogFilters | 136 -- .../method/messages.getDialogUnreadMarks | 133 -- .../messages.getEmojiKeywordsDifference | 154 -- .../method/messages.getFullChat | 172 -- .../method/messages.getGameHighScores | 187 -- .../method/messages.getInlineGameHighScores | 177 -- .../method/messages.getMessagesReactions | 153 -- .../method/messages.getPeerDialogs | 186 -- .../method/messages.getReplies | 196 -- .../method/messages.getStickerSet | 167 -- .../method/messages.installStickerSet | 172 -- .../method/messages.readFeaturedStickers | 150 -- .../core.telegram.org/method/messages.saveGif | 172 -- .../method/messages.searchGifs | 172 -- .../method/messages.sendBroadcast | 145 -- .../method/messages.sendEncrypted | 205 -- .../method/messages.sendMultiMedia | 238 -- .../method/messages.sendVote | 205 -- .../method/messages.uninstallStickerSet | 167 -- .../method/messages.updateDialogFiltersOrder | 153 -- .../method/payments.getBankCardData | 149 -- .../method/phone.getCallConfig | 134 -- .../method/phone.saveCallDebug | 177 -- .../method/photos.deletePhotos | 148 -- .../method/stats.getMegagroupStats | 165 -- .../method/stats.getMessagePublicForwards | 208 -- data/core.telegram.org/methods.html | 2084 ----------------- data/core.telegram.org/mtproto/TL-types.html | 124 - data/core.telegram.org/mtproto_v1.html | 229 -- data/core.telegram.org/passport.html | 690 ------ .../passport/sdk-android.html | 180 -- data/core.telegram.org/tdlib.html | 147 -- data/core.telegram.org/type/CdnPublicKey.html | 145 -- data/core.telegram.org/type/ChatInvite.html | 172 -- data/core.telegram.org/type/DcOption.html | 143 -- .../type/DecryptedMessage.html | 140 -- .../type/DecryptedMessageMedia.html | 149 -- .../type/InputEncryptedFile.html | 158 -- .../type/InputPhoneCall.html | 143 -- .../type/InputWallPaper.html | 153 -- data/core.telegram.org/type/LabeledPrice.html | 143 -- .../type/LangPackDifference.html | 167 -- .../core.telegram.org/type/MessageEntity.html | 233 -- .../type/MessageInteractionCounters.html | 143 -- data/core.telegram.org/type/MessageMedia.html | 227 -- .../type/MessageReactionsList.html | 128 - data/core.telegram.org/type/Page.html | 143 -- data/core.telegram.org/type/Peer.html | 153 -- data/core.telegram.org/type/PhoneCall.html | 168 -- data/core.telegram.org/type/PhotoSize.html | 168 -- .../type/SendMessageAction.html | 203 -- data/core.telegram.org/type/account.Password | 162 -- .../type/account.TmpPassword | 162 -- data/core.telegram.org/type/help.PromoData | 167 -- data/core.telegram.org/type/int.html | 118 - data/core.telegram.org/type/messages.ChatFull | 168 -- .../type/messages.FavedStickers | 167 -- .../type/messages.FoundStickerSets | 167 -- data/core.telegram.org/type/messages.Messages | 229 -- .../type/messages.PeerDialogs | 167 -- .../core.telegram.org/type/messages.VotesList | 162 -- .../core.telegram.org/type/payments.SavedInfo | 162 -- data/core.telegram.org/type/string.html | 126 - data/core.telegram.org/type/upload.CdnFile | 167 -- data/telegram.org/blog/edit.html | 245 -- data/telegram.org/blog/inline-bots.html | 234 -- data/telegram.org/blog/polls-2-0-vmq.html | 271 --- data/telegram.org/faq.html | 705 ------ data/telegram.org/faq_spam.html | 163 -- 190 files changed, 34462 deletions(-) delete mode 100644 data/core.telegram.org/api/end-to-end/video-calls.html delete mode 100644 data/core.telegram.org/api/pfs.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/url-authorization.html delete mode 100644 data/core.telegram.org/bots/inline.html delete mode 100644 data/core.telegram.org/bots/webhooks.html delete mode 100644 data/core.telegram.org/constructor/account.tmpPassword delete mode 100644 data/core.telegram.org/constructor/account.wallPapersNotModified delete mode 100644 data/core.telegram.org/constructor/accountDaysTTL.html delete mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeCall delete mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaVenue.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantBanned.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsBanned.html delete mode 100644 data/core.telegram.org/constructor/channels.channelParticipant delete mode 100644 data/core.telegram.org/constructor/chatEmpty.html delete mode 100644 data/core.telegram.org/constructor/chatParticipants.html delete mode 100644 data/core.telegram.org/constructor/contacts.contacts delete mode 100644 data/core.telegram.org/constructor/contacts.found 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/disabledFeature.html delete mode 100644 data/core.telegram.org/constructor/documentEmpty.html delete mode 100644 data/core.telegram.org/constructor/emojiKeyword.html delete mode 100644 data/core.telegram.org/constructor/encryptedChatDiscarded.html delete mode 100644 data/core.telegram.org/constructor/encryptedFileEmpty.html delete mode 100644 data/core.telegram.org/constructor/exportedMessageLink.html delete mode 100644 data/core.telegram.org/constructor/fileLocation.html delete mode 100644 data/core.telegram.org/constructor/help.passportConfigNotModified delete mode 100644 data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty delete mode 100644 data/core.telegram.org/constructor/inputAppEvent.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/inputEncryptedFileUploaded.html delete mode 100644 data/core.telegram.org/constructor/inputMediaDocumentExternal.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputPeerEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.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/inputUserFromMessage.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/jsonNull.html delete mode 100644 data/core.telegram.org/constructor/jsonObject.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonGame.html delete mode 100644 data/core.telegram.org/constructor/messageActionCustomAction.html delete mode 100644 data/core.telegram.org/constructor/messageActionGameScore.html delete mode 100644 data/core.telegram.org/constructor/messageEntityBotCommand.html delete mode 100644 data/core.telegram.org/constructor/messageFwdHeader.html delete mode 100644 data/core.telegram.org/constructor/messageMediaPhoto.html delete mode 100644 data/core.telegram.org/constructor/messageMediaUnsupported.html delete mode 100644 data/core.telegram.org/constructor/messages.chats 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.sentEncryptedMessage delete mode 100644 data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive delete mode 100644 data/core.telegram.org/constructor/notifyUsers.html delete mode 100644 data/core.telegram.org/constructor/pageBlockAnchor.html delete mode 100644 data/core.telegram.org/constructor/pageBlockOrderedList.html delete mode 100644 data/core.telegram.org/constructor/pageBlockSubtitle.html delete mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html delete mode 100644 data/core.telegram.org/constructor/phoneCallProtocol.html delete mode 100644 data/core.telegram.org/constructor/phoneConnectionWebrtc.html delete mode 100644 data/core.telegram.org/constructor/photoEmpty.html delete mode 100644 data/core.telegram.org/constructor/photos.photos delete mode 100644 data/core.telegram.org/constructor/pollAnswer.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/secureValueTypeIdentityCard.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html delete mode 100644 data/core.telegram.org/constructor/sendMessageGamePlayAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html delete mode 100644 data/core.telegram.org/constructor/statsGraphAsync.html 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/textItalic.html delete mode 100644 data/core.telegram.org/constructor/textMarked.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryBotsPM.html delete mode 100644 data/core.telegram.org/constructor/updateChannelUserTyping.html delete mode 100644 data/core.telegram.org/constructor/updateChatParticipants.html delete mode 100644 data/core.telegram.org/constructor/updateDeleteMessages.html delete mode 100644 data/core.telegram.org/constructor/updateEditChannelMessage.html delete mode 100644 data/core.telegram.org/constructor/updateEncryption.html delete mode 100644 data/core.telegram.org/constructor/updateGeoLiveViewed.html delete mode 100644 data/core.telegram.org/constructor/updateReadFeaturedStickers.html delete mode 100644 data/core.telegram.org/constructor/updateServiceNotification.html delete mode 100644 data/core.telegram.org/constructor/updateUserTyping.html delete mode 100644 data/core.telegram.org/constructor/updates.differenceSlice delete mode 100644 data/core.telegram.org/constructor/upload.fileCdnRedirect 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/userStatusOffline.html delete mode 100644 data/core.telegram.org/constructor/vector.html delete mode 100644 data/core.telegram.org/method/account.deleteSecureValue delete mode 100644 data/core.telegram.org/method/account.getAccountTTL delete mode 100644 data/core.telegram.org/method/account.getNotifySettings delete mode 100644 data/core.telegram.org/method/account.resendPasswordEmail delete mode 100644 data/core.telegram.org/method/account.setPrivacy delete mode 100644 data/core.telegram.org/method/account.updatePasswordSettings delete mode 100644 data/core.telegram.org/method/account.updateUsername delete mode 100644 data/core.telegram.org/method/account.verifyPhone delete mode 100644 data/core.telegram.org/method/auth.checkPhone delete mode 100644 data/core.telegram.org/method/auth.importLoginToken delete mode 100644 data/core.telegram.org/method/channels.getGroupsForDiscussion delete mode 100644 data/core.telegram.org/method/channels.togglePreHistoryHidden delete mode 100644 data/core.telegram.org/method/contacts.resetTopPeerRating delete mode 100644 data/core.telegram.org/method/folders.deleteFolder delete mode 100644 data/core.telegram.org/method/langpack.getLanguage 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.deleteHistory 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.getAllStickers 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.getEmojiKeywordsDifference 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.getInlineGameHighScores delete mode 100644 data/core.telegram.org/method/messages.getMessagesReactions delete mode 100644 data/core.telegram.org/method/messages.getPeerDialogs delete mode 100644 data/core.telegram.org/method/messages.getReplies delete mode 100644 data/core.telegram.org/method/messages.getStickerSet delete mode 100644 data/core.telegram.org/method/messages.installStickerSet delete mode 100644 data/core.telegram.org/method/messages.readFeaturedStickers delete mode 100644 data/core.telegram.org/method/messages.saveGif delete mode 100644 data/core.telegram.org/method/messages.searchGifs 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.sendMultiMedia delete mode 100644 data/core.telegram.org/method/messages.sendVote delete mode 100644 data/core.telegram.org/method/messages.uninstallStickerSet delete mode 100644 data/core.telegram.org/method/messages.updateDialogFiltersOrder delete mode 100644 data/core.telegram.org/method/payments.getBankCardData delete mode 100644 data/core.telegram.org/method/phone.getCallConfig delete mode 100644 data/core.telegram.org/method/phone.saveCallDebug delete mode 100644 data/core.telegram.org/method/photos.deletePhotos 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/methods.html delete mode 100644 data/core.telegram.org/mtproto/TL-types.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/sdk-android.html delete mode 100644 data/core.telegram.org/tdlib.html delete mode 100644 data/core.telegram.org/type/CdnPublicKey.html delete mode 100644 data/core.telegram.org/type/ChatInvite.html delete mode 100644 data/core.telegram.org/type/DcOption.html delete mode 100644 data/core.telegram.org/type/DecryptedMessage.html delete mode 100644 data/core.telegram.org/type/DecryptedMessageMedia.html delete mode 100644 data/core.telegram.org/type/InputEncryptedFile.html delete mode 100644 data/core.telegram.org/type/InputPhoneCall.html delete mode 100644 data/core.telegram.org/type/InputWallPaper.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/MessageEntity.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/MessageReactionsList.html delete mode 100644 data/core.telegram.org/type/Page.html delete mode 100644 data/core.telegram.org/type/Peer.html delete mode 100644 data/core.telegram.org/type/PhoneCall.html delete mode 100644 data/core.telegram.org/type/PhotoSize.html delete mode 100644 data/core.telegram.org/type/SendMessageAction.html delete mode 100644 data/core.telegram.org/type/account.Password delete mode 100644 data/core.telegram.org/type/account.TmpPassword delete mode 100644 data/core.telegram.org/type/help.PromoData delete mode 100644 data/core.telegram.org/type/int.html delete mode 100644 data/core.telegram.org/type/messages.ChatFull delete mode 100644 data/core.telegram.org/type/messages.FavedStickers delete mode 100644 data/core.telegram.org/type/messages.FoundStickerSets 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.VotesList delete mode 100644 data/core.telegram.org/type/payments.SavedInfo delete mode 100644 data/core.telegram.org/type/string.html delete mode 100644 data/core.telegram.org/type/upload.CdnFile delete mode 100644 data/telegram.org/blog/edit.html delete mode 100644 data/telegram.org/blog/inline-bots.html delete mode 100644 data/telegram.org/blog/polls-2-0-vmq.html delete mode 100644 data/telegram.org/faq.html delete mode 100644 data/telegram.org/faq_spam.html 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/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/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/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/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/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/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.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/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.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/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/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/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/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/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/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/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/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/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/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.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.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/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/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/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/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/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/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/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/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.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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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.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.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.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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/method/account.deleteSecureValue b/data/core.telegram.org/method/account.deleteSecureValue deleted file mode 100644 index 78db756959..0000000000 --- a/data/core.telegram.org/method/account.deleteSecureValue +++ /dev/null @@ -1,153 +0,0 @@ - - - - - account.deleteSecureValue - - - - - - - - - - - - - -
- -
-
-
- -

account.deleteSecureValue

- -

Delete stored Telegram Passport documents, for more info see the passport docs »

-

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
typesVector<SecureValueType>Document types to delete
-

Result

-

Bool

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getAccountTTL b/data/core.telegram.org/method/account.getAccountTTL deleted file mode 100644 index 3dbae6ebf3..0000000000 --- a/data/core.telegram.org/method/account.getAccountTTL +++ /dev/null @@ -1,134 +0,0 @@ - - - - - account.getAccountTTL - - - - - - - - - - - - - -
- -
-
-
- -

account.getAccountTTL

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getNotifySettings b/data/core.telegram.org/method/account.getNotifySettings deleted file mode 100644 index 96dae23deb..0000000000 --- a/data/core.telegram.org/method/account.getNotifySettings +++ /dev/null @@ -1,166 +0,0 @@ - - - - - account.getNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

account.getNotifySettings

- -

Gets current notification settings for a given user/group, from all users/all groups.

-

-
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;
----functions---
-account.getNotifySettings#12b3ad31 peer:InputNotifyPeer = PeerNotifySettings;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputNotifyPeerNotification source
-

Result

-

Returns a PeerNotifySettings object containing current notification settings.

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.resendPasswordEmail b/data/core.telegram.org/method/account.resendPasswordEmail deleted file mode 100644 index 1c5c6fdea2..0000000000 --- a/data/core.telegram.org/method/account.resendPasswordEmail +++ /dev/null @@ -1,138 +0,0 @@ - - - - - account.resendPasswordEmail - - - - - - - - - - - - - -
- -
-
-
- -

account.resendPasswordEmail

- -

Resend the code to verify an email to use as 2FA recovery method.

-

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.resendPasswordEmail#7a7f2a15 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Related pages

-

Two-factor authentication

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.setPrivacy b/data/core.telegram.org/method/account.setPrivacy deleted file mode 100644 index a5e2a910e1..0000000000 --- a/data/core.telegram.org/method/account.setPrivacy +++ /dev/null @@ -1,176 +0,0 @@ - - - - - account.setPrivacy - - - - - - - - - - - - - -
- -
-
-
- -

account.setPrivacy

- -

Change privacy settings of current account

-

-
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
----functions---
-account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keyInputPrivacyKeyPeers to which the privacy rules apply
rulesVector<InputPrivacyRule>New privacy rules
-

Result

-

account.PrivacyRules

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PRIVACY_KEY_INVALIDThe privacy key is invalid
400PRIVACY_VALUE_INVALIDThe specified privacy rule combination is invalid
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.updatePasswordSettings b/data/core.telegram.org/method/account.updatePasswordSettings deleted file mode 100644 index 15a14c1f6a..0000000000 --- a/data/core.telegram.org/method/account.updatePasswordSettings +++ /dev/null @@ -1,202 +0,0 @@ - - - - - account.updatePasswordSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.updatePasswordSettings

- -

Set a new 2FA password

-

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
passwordInputCheckPasswordSRPThe old password (see SRP)
new_settingsaccount.PasswordInputSettingsThe new password (see SRP)
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400EMAIL_UNCONFIRMEDEmail unconfirmed
400EMAIL_UNCONFIRMED_XThe provided email isn't confirmed, X is the length of the verification code that was just sent to the email: use account.verifyEmail to enter the received verification code and enable the recovery email.
400NEW_SALT_INVALIDThe new salt is invalid
400NEW_SETTINGS_INVALIDThe new password settings are invalid
400PASSWORD_HASH_INVALIDThe old password hash is invalid
400SRP_ID_INVALIDInvalid SRP ID provided
-

Related pages

-

Two-factor authentication

-

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

-

account.verifyEmail

-

Verify an email address for telegram passport.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.updateUsername b/data/core.telegram.org/method/account.updateUsername deleted file mode 100644 index b9610d71bf..0000000000 --- a/data/core.telegram.org/method/account.updateUsername +++ /dev/null @@ -1,182 +0,0 @@ - - - - - account.updateUsername - - - - - - - - - - - - - -
- -
-
-
- -

account.updateUsername

- -

Changes username for the current user.

-

-
userEmpty#200250ba id:int = 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;
----functions---
-account.updateUsername#3e0bdd7c username:string = User;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usernamestringusername or empty string if username is to be removed
Accepted characters: a-z (case-insensitive), 0-9 and underscores.
Length: 5-32 characters.
-

Result

-

Returns updated information on the user in a User type object.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400USERNAME_INVALIDUnacceptable username
400USERNAME_NOT_MODIFIEDUsername is not different from the current username
400USERNAME_OCCUPIEDUsername is taken
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.verifyPhone b/data/core.telegram.org/method/account.verifyPhone deleted file mode 100644 index 62534d886f..0000000000 --- a/data/core.telegram.org/method/account.verifyPhone +++ /dev/null @@ -1,181 +0,0 @@ - - - - - account.verifyPhone - - - - - - - - - - - - - -
- -
-
-
- -

account.verifyPhone

- -

Verify a phone number for telegram passport.

-

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
phone_code_hashstringPhone code hash received from the call to account.sendVerifyPhoneCode
phone_codestringCode received after the call to account.sendVerifyPhoneCode
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars)
-

Related pages

-

account.sendVerifyPhoneCode

-

Send the verification phone code for telegram passport.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.checkPhone b/data/core.telegram.org/method/auth.checkPhone deleted file mode 100644 index 491df9a75e..0000000000 --- a/data/core.telegram.org/method/auth.checkPhone +++ /dev/null @@ -1,176 +0,0 @@ - - - - - auth.checkPhone - - - - - - - - - - - - - -
- -
-
-
- -

auth.checkPhone

- -

Returns information on whether the passed phone number was registered.

-

-
 Method schema is available as of layer 78. Switch »

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number in the international format
-

Result

-

The method returns an auth.CheckedPhone type object with information on whether an account with such a phone number has already been registered, as well as whether invitations were sent to this number (using the auth.sendInvites method).

-

Query example

-
(auth.checkPhone "79123413132")
-=
-(auth.checkedPhone
-  phone_registered:(boolFalse)
-  phone_invited:(boolFalse)
-)
-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_NUMBER_BANNEDThe provided phone number is banned from telegram
400PHONE_NUMBER_INVALIDInvalid phone number
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.importLoginToken b/data/core.telegram.org/method/auth.importLoginToken deleted file mode 100644 index 01250ed9df..0000000000 --- a/data/core.telegram.org/method/auth.importLoginToken +++ /dev/null @@ -1,172 +0,0 @@ - - - - - auth.importLoginToken - - - - - - - - - - - - - -
- -
-
-
- -

auth.importLoginToken

- -

Login using a redirected login token, generated in case of DC mismatch during QR code login.

-

For more info, see login via QR code.

-

-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
-auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
-auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
----functions---
-auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
tokenbytesLogin token
-

Result

-

auth.LoginToken

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400AUTH_TOKEN_EXPIREDThe authorization token has expired
-

Related pages

-

Login via QR code

-

QR code login flow

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.getGroupsForDiscussion b/data/core.telegram.org/method/channels.getGroupsForDiscussion deleted file mode 100644 index d285b885d6..0000000000 --- a/data/core.telegram.org/method/channels.getGroupsForDiscussion +++ /dev/null @@ -1,144 +0,0 @@ - - - - - channels.getGroupsForDiscussion - - - - - - - - - - - - - -
- -
-
-
- -

channels.getGroupsForDiscussion

- -

Get all groups that can be used as discussion groups.

-

Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
-To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first.

-

-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-channels.getGroupsForDiscussion#f5dad378 = messages.Chats;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

messages.Chats

-

Related pages

-

Discussion groups

-

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

-

Channels

-

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

-

channels.togglePreHistoryHidden

-

Hide/unhide message history for new channel/supergroup users

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.togglePreHistoryHidden b/data/core.telegram.org/method/channels.togglePreHistoryHidden deleted file mode 100644 index 76348d4ba8..0000000000 --- a/data/core.telegram.org/method/channels.togglePreHistoryHidden +++ /dev/null @@ -1,202 +0,0 @@ - - - - - channels.togglePreHistoryHidden - - - - - - - - - - - - - -
- -
-
-
- -

channels.togglePreHistoryHidden

- -

Hide/unhide message history for new channel/supergroup users

-

-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#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;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = 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;
----functions---
-channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
enabledBoolHide/unhide
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this
400CHAT_ID_INVALIDThe provided chat id is invalid
400CHAT_LINK_EXISTSThe chat is public, you can't hide the history to new users
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.resetTopPeerRating b/data/core.telegram.org/method/contacts.resetTopPeerRating deleted file mode 100644 index 21814e6f58..0000000000 --- a/data/core.telegram.org/method/contacts.resetTopPeerRating +++ /dev/null @@ -1,175 +0,0 @@ - - - - - contacts.resetTopPeerRating - - - - - - - - - - - - - -
- -
-
-
- -

contacts.resetTopPeerRating

- -

Reset rating of top peer

-

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
categoryTopPeerCategoryTop peer category
peerInputPeerPeer whose rating should be reset
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid
-

Related pages

-

Top peer rating

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/folders.deleteFolder b/data/core.telegram.org/method/folders.deleteFolder deleted file mode 100644 index 3c6780e30c..0000000000 --- a/data/core.telegram.org/method/folders.deleteFolder +++ /dev/null @@ -1,158 +0,0 @@ - - - - - folders.deleteFolder - - - - - - - - - - - - - -
- -
-
-
- -

folders.deleteFolder

- -

Delete a peer folder

-

-
updatesTooLong#e317af7e = 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;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = 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;
----functions---
-folders.deleteFolder#1c295881 folder_id:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_idintPeer folder ID, for more info click here
-

Result

-

Updates

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/langpack.getLanguage b/data/core.telegram.org/method/langpack.getLanguage deleted file mode 100644 index 8956ca2072..0000000000 --- a/data/core.telegram.org/method/langpack.getLanguage +++ /dev/null @@ -1,154 +0,0 @@ - - - - - langpack.getLanguage - - - - - - - - - - - - - -
- -
-
-
- -

langpack.getLanguage

- -

Get information about a language in a localization pack

-

-
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
----functions---
-langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
-

Result

-

LangPackLanguage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.acceptUrlAuth b/data/core.telegram.org/method/messages.acceptUrlAuth deleted file mode 100644 index 5d3261666c..0000000000 --- a/data/core.telegram.org/method/messages.acceptUrlAuth +++ /dev/null @@ -1,174 +0,0 @@ - - - - - messages.acceptUrlAuth - - - - - - - - - - - - - -
- -
-
-
- -

messages.acceptUrlAuth

- -

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

-

-
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
-urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
-urlAuthResultDefault#a9d6db1f = UrlAuthResult;
----functions---
-messages.acceptUrlAuth#f729ea98 flags:# write_allowed:flags.0?true peer:InputPeer msg_id:int button_id:int = UrlAuthResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
write_allowedflags.0?trueSet this flag to allow the bot to send messages to you (if requested)
peerInputPeerThe location of the message
msg_idintMessage ID of the message with the login button
button_idintID of the login button
-

Result

-

UrlAuthResult

-

Related pages

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.addChatUser b/data/core.telegram.org/method/messages.addChatUser deleted file mode 100644 index 54250f1f87..0000000000 --- a/data/core.telegram.org/method/messages.addChatUser +++ /dev/null @@ -1,227 +0,0 @@ - - - - - messages.addChatUser - - - - - - - - - - - - - -
- -
-
-
- -

messages.addChatUser

- -

Adds a user to a chat and sends a service message on it.

-

-
updatesTooLong#e317af7e = 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;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = 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;
----functions---
-messages.addChatUser#f9a0aa09 chat_id:int user_id:InputUser fwd_limit:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintChat ID
user_idInputUserUser ID to be added
fwd_limitintNumber of last messages to be forwarded
-

Result

-

messages.StatedMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this
400CHAT_ID_INVALIDThe provided chat id is invalid
403CHAT_WRITE_FORBIDDENYou can't write in this chat
400INPUT_USER_DEACTIVATEDThe specified user was deleted
400PEER_ID_INVALIDThe provided peer id is invalid
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example)
400USER_ALREADY_PARTICIPANTThe user is already in the group
400USER_ID_INVALIDThe provided user ID is invalid
403USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.deleteHistory b/data/core.telegram.org/method/messages.deleteHistory deleted file mode 100644 index a58dc9709e..0000000000 --- a/data/core.telegram.org/method/messages.deleteHistory +++ /dev/null @@ -1,201 +0,0 @@ - - - - - messages.deleteHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.deleteHistory

- -

Deletes communication history.

-

-
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
----functions---
-messages.deleteHistory#1c015b09 flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int = messages.AffectedHistory;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
just_clearflags.0?trueJust clear history for the current user, without actually removing messages for every chat user
revokeflags.1?trueWhether to delete the message history for all chat participants
peerInputPeerUser or chat, communication history of which will be deleted
max_idintMaximum ID of message to delete
-

Result

-

messages.AffectedHistory

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid
400MESSAGE_ID_INVALIDThe provided message id is invalid
400MSG_ID_INVALIDInvalid message ID provided
400PEER_ID_INVALIDThe provided peer id is invalid
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.editMessage b/data/core.telegram.org/method/messages.editMessage deleted file mode 100644 index 8449d15253..0000000000 --- a/data/core.telegram.org/method/messages.editMessage +++ /dev/null @@ -1,323 +0,0 @@ - - - - - messages.editMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.editMessage

- -

Edit message

-

-
updatesTooLong#e317af7e = 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;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = 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;
----functions---
-messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueDisable webpage preview
peerInputPeerWhere was the message sent
idintID of the message to edit
messageflags.11?stringNew message
mediaflags.14?InputMediaNew attached media
reply_markupflags.2?ReplyMarkupReply markup for inline keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
schedule_dateflags.15?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid
400BUTTON_URL_INVALIDButton URL invalid
400CHANNEL_INVALIDThe provided channel is invalid
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this
403CHAT_WRITE_FORBIDDENYou can't write in this chat
403INLINE_BOT_REQUIREDOnly the inline bot can edit message
400INPUT_USER_DEACTIVATEDThe specified user was deleted
400MEDIA_CAPTION_TOO_LONGThe caption is too long
400MEDIA_PREV_INVALIDPrevious media invalid
403MESSAGE_AUTHOR_REQUIREDMessage author required
400MESSAGE_EDIT_TIME_EXPIREDYou can't edit this message anymore, too much time has passed since its creation.
400MESSAGE_EMPTYThe provided message is empty
400MESSAGE_ID_INVALIDThe provided message id is invalid
400MESSAGE_NOT_MODIFIEDThe message text has not changed
400MESSAGE_TOO_LONGThe provided message is too long
400MSG_ID_INVALIDInvalid message ID provided
400PEER_ID_INVALIDThe provided peer id is invalid
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid
400SCHEDULE_DATE_INVALIDInvalid schedule date provided
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels
-

Bots can use this method

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Scheduled messages

-

Telegram allows scheduling messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.exportChatInvite b/data/core.telegram.org/method/messages.exportChatInvite deleted file mode 100644 index 3e7ae4d63c..0000000000 --- a/data/core.telegram.org/method/messages.exportChatInvite +++ /dev/null @@ -1,188 +0,0 @@ - - - - - messages.exportChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.exportChatInvite

- -

Export an invite link for a chat

-

-
chatInviteEmpty#69df3769 = ExportedChatInvite;
-chatInviteExported#fc2e05bc link:string = ExportedChatInvite;
----functions---
-messages.exportChatInvite#df7534c peer:InputPeer = ExportedChatInvite;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerChat
-

Result

-

ExportedChatInvite

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this
400CHAT_ID_INVALIDThe provided chat id is invalid
403CHAT_WRITE_FORBIDDENYou can't write in this chat
400PEER_ID_INVALIDThe provided peer id is invalid
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getAllStickers b/data/core.telegram.org/method/messages.getAllStickers deleted file mode 100644 index 1562371662..0000000000 --- a/data/core.telegram.org/method/messages.getAllStickers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getAllStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getAllStickers

- -

Get all installed stickers

-

-
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
-messages.allStickers#edfd405f hash:int sets:Vector<StickerSet> = messages.AllStickers;
----functions---
-messages.getAllStickers#1c9618b1 hash:int = messages.AllStickers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
-

Result

-

messages.AllStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getDialogFilters b/data/core.telegram.org/method/messages.getDialogFilters deleted file mode 100644 index ef2317603d..0000000000 --- a/data/core.telegram.org/method/messages.getDialogFilters +++ /dev/null @@ -1,136 +0,0 @@ - - - - - messages.getDialogFilters - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDialogFilters

- -

Get folders

-

-
---functions---
-messages.getDialogFilters#f19ed96d = Vector<DialogFilter>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<DialogFilter>

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getDialogUnreadMarks b/data/core.telegram.org/method/messages.getDialogUnreadMarks deleted file mode 100644 index 0c2cef4602..0000000000 --- a/data/core.telegram.org/method/messages.getDialogUnreadMarks +++ /dev/null @@ -1,133 +0,0 @@ - - - - - messages.getDialogUnreadMarks - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDialogUnreadMarks

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getEmojiKeywordsDifference b/data/core.telegram.org/method/messages.getEmojiKeywordsDifference deleted file mode 100644 index 0315ae38bd..0000000000 --- a/data/core.telegram.org/method/messages.getEmojiKeywordsDifference +++ /dev/null @@ -1,154 +0,0 @@ - - - - - messages.getEmojiKeywordsDifference - - - - - - - - - - - - - -
- -
-
-
- -

messages.getEmojiKeywordsDifference

- -

Get changed emoji keywords

-

-
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
----functions---
-messages.getEmojiKeywordsDifference#1508b6af lang_code:string from_version:int = EmojiKeywordsDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
from_versionintPrevious emoji keyword localization version
-

Result

-

EmojiKeywordsDifference

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getFullChat b/data/core.telegram.org/method/messages.getFullChat deleted file mode 100644 index 03fbb3866f..0000000000 --- a/data/core.telegram.org/method/messages.getFullChat +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.getFullChat - - - - - - - - - - - - - -
- -
-
-
- -

messages.getFullChat

- -

Returns full chat info according to its ID.

-

-
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
----functions---
-messages.getFullChat#3b831c66 chat_id:int = messages.ChatFull;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintChat ID
-

Result

-

messages.ChatFull

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid
400PEER_ID_INVALIDThe provided peer id is invalid
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getGameHighScores b/data/core.telegram.org/method/messages.getGameHighScores deleted file mode 100644 index 1a1f257dae..0000000000 --- a/data/core.telegram.org/method/messages.getGameHighScores +++ /dev/null @@ -1,187 +0,0 @@ - - - - - messages.getGameHighScores - - - - - - - - - - - - - -
- -
-
-
- -

messages.getGameHighScores

- -

Get highscores of a game

-

-
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
----functions---
-messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerWhere was the game sent
idintID of message with game media attachment
user_idInputUserGet high scores made by a certain user
-

Result

-

messages.HighScores

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid
400PEER_ID_INVALIDThe provided peer id is invalid
400USER_BOT_REQUIREDThis method can only be called by a bot
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getInlineGameHighScores b/data/core.telegram.org/method/messages.getInlineGameHighScores deleted file mode 100644 index 4a25939a9d..0000000000 --- a/data/core.telegram.org/method/messages.getInlineGameHighScores +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.getInlineGameHighScores - - - - - - - - - - - - - -
- -
-
-
- -

messages.getInlineGameHighScores

- -

Get highscores of a game sent using an inline bot

-

-
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
----functions---
-messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idInputBotInlineMessageIDID of inline message
user_idInputUserGet high scores of a certain user
-

Result

-

messages.HighScores

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid
400USER_BOT_REQUIREDThis method can only be called by a bot
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getMessagesReactions b/data/core.telegram.org/method/messages.getMessagesReactions deleted file mode 100644 index 58119d44fd..0000000000 --- a/data/core.telegram.org/method/messages.getMessagesReactions +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getMessagesReactions - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessagesReactions

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getPeerDialogs b/data/core.telegram.org/method/messages.getPeerDialogs deleted file mode 100644 index f9d6c7b96b..0000000000 --- a/data/core.telegram.org/method/messages.getPeerDialogs +++ /dev/null @@ -1,186 +0,0 @@ - - - - - messages.getPeerDialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.getPeerDialogs

- -

Get dialog info of specified peers

-

-
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
----functions---
-messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peersVector<InputDialogPeer>Peers
-

Result

-

messages.PeerDialogs

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup
400CONNECTION_DEVICE_MODEL_EMPTYDevice model empty
400MSG_ID_INVALIDInvalid message ID provided
400PEER_ID_INVALIDThe provided peer id is invalid
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getReplies b/data/core.telegram.org/method/messages.getReplies deleted file mode 100644 index d306338ee7..0000000000 --- a/data/core.telegram.org/method/messages.getReplies +++ /dev/null @@ -1,196 +0,0 @@ - - - - - messages.getReplies - - - - - - - - - - - - - -
- -
-
-
- -

messages.getReplies

- -

Get messages in a reply thread

-

-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getReplies#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;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
msg_idintMessage ID
offset_idintOffsets for pagination, for more info click here
offset_dateintOffsets for pagination, for more info click here
add_offsetintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
max_idintIf a positive value was transferred, the method will return only messages with ID smaller than max_id
min_idintIf a positive value was transferred, the method will return only messages with ID bigger than min_id
hashintHash for pagination, for more info click here
-

Result

-

messages.Messages

-

Bots can use this method

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getStickerSet b/data/core.telegram.org/method/messages.getStickerSet deleted file mode 100644 index 51473bd8fb..0000000000 --- a/data/core.telegram.org/method/messages.getStickerSet +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.getStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

messages.getStickerSet

- -

Get info about a stickerset

-

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

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetStickerset
-

Result

-

messages.StickerSet

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.installStickerSet b/data/core.telegram.org/method/messages.installStickerSet deleted file mode 100644 index 73c736f778..0000000000 --- a/data/core.telegram.org/method/messages.installStickerSet +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.installStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

messages.installStickerSet

- -

Install a stickerset

-

-
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;
-messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;
----functions---
-messages.installStickerSet#c78fe460 stickerset:InputStickerSet archived:Bool = messages.StickerSetInstallResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetStickerset to install
archivedBoolWhether to archive stickerset
-

Result

-

messages.StickerSetInstallResult

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.readFeaturedStickers b/data/core.telegram.org/method/messages.readFeaturedStickers deleted file mode 100644 index 60bb3066ad..0000000000 --- a/data/core.telegram.org/method/messages.readFeaturedStickers +++ /dev/null @@ -1,150 +0,0 @@ - - - - - messages.readFeaturedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.readFeaturedStickers

- -

Mark new featured stickers as read

-

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.readFeaturedStickers#5b118126 id:Vector<long> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<long>IDs of stickersets to mark as read
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.saveGif b/data/core.telegram.org/method/messages.saveGif deleted file mode 100644 index 458594c409..0000000000 --- a/data/core.telegram.org/method/messages.saveGif +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.saveGif - - - - - - - - - - - - - -
- -
-
-
- -

messages.saveGif

- -

Add GIF to saved gifs list

-

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idInputDocumentGIF to save
unsaveBoolWhether to remove GIF from saved gifs list
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400GIF_ID_INVALIDThe provided GIF ID is invalid
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.searchGifs b/data/core.telegram.org/method/messages.searchGifs deleted file mode 100644 index b57a14a06b..0000000000 --- a/data/core.telegram.org/method/messages.searchGifs +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.searchGifs - - - - - - - - - - - - - -
- -
-
-
- -

messages.searchGifs

- -

Search for GIFs

-

-
 Method schema is available as of layer 114. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
qstringText query
offsetintOffset for pagination »
-

Result

-

messages.FoundGifs

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400SEARCH_QUERY_EMPTYThe search query is empty
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendBroadcast b/data/core.telegram.org/method/messages.sendBroadcast deleted file mode 100644 index 503ca35f2c..0000000000 --- a/data/core.telegram.org/method/messages.sendBroadcast +++ /dev/null @@ -1,145 +0,0 @@ - - - - - messages.sendBroadcast - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendBroadcast

- -

Sends multiple messages to contacts.

-

{scheme}

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
contactsVector<InputUser>List of user ID to whom a message will be sent
messagestringMessage text
mediaInputMediaMessage media-contents
-

Result

-

messages.StatedMessages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendEncrypted b/data/core.telegram.org/method/messages.sendEncrypted deleted file mode 100644 index c9c912c675..0000000000 --- a/data/core.telegram.org/method/messages.sendEncrypted +++ /dev/null @@ -1,205 +0,0 @@ - - - - - messages.sendEncrypted - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendEncrypted

- -

Sends a text message to a secret chat.

-

-
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
-messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
----functions---
-messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?trueSend encrypted message without a notification
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID, necessary to avoid message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key that was created during chat initialization
-

Result

-

messages.SentEncryptedMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid
400DATA_INVALIDEncrypted data invalid
400ENCRYPTION_DECLINEDThe secret chat was declined
400MSG_WAIT_FAILEDA waiting call returned an error
-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendMultiMedia b/data/core.telegram.org/method/messages.sendMultiMedia deleted file mode 100644 index 91e89616e5..0000000000 --- a/data/core.telegram.org/method/messages.sendMultiMedia +++ /dev/null @@ -1,238 +0,0 @@ - - - - - messages.sendMultiMedia - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendMultiMedia

- -

Send an album or grouped media

-

-
updatesTooLong#e317af7e = 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;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = 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;
----functions---
-messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send the album silently (no notification triggered)
backgroundflags.6?trueSend in background?
clear_draftflags.7?trueWhether to clear drafts
peerInputPeerThe destination chat
reply_to_msg_idflags.0?intThe message to reply to
multi_mediaVector<InputSingleMedia>The medias to send
schedule_dateflags.10?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this
400MEDIA_EMPTYThe provided media object is invalid
400MEDIA_INVALIDMedia invalid
400MULTI_MEDIA_TOO_LONGToo many media files for album
400PEER_ID_INVALIDThe provided peer id is invalid
400RANDOM_ID_EMPTYRandom ID empty
-

Bots can use this method

-

Related pages

-

Message drafts

-

How to handle message drafts

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendVote b/data/core.telegram.org/method/messages.sendVote deleted file mode 100644 index 3e46d769ad..0000000000 --- a/data/core.telegram.org/method/messages.sendVote +++ /dev/null @@ -1,205 +0,0 @@ - - - - - messages.sendVote - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendVote

- -

Vote in a poll

-

-
updatesTooLong#e317af7e = 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;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = 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;
----functions---
-messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the poll was sent
msg_idintThe message ID of the poll
optionsVector<bytes>The options that were chosen
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid
400MESSAGE_POLL_CLOSEDPoll closed
400OPTIONS_TOO_MUCHToo many options provided
400OPTION_INVALIDInvalid option selected
400REVOTE_NOT_ALLOWEDYou cannot change your vote
-

Related pages

-

poll

-

Poll

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.uninstallStickerSet b/data/core.telegram.org/method/messages.uninstallStickerSet deleted file mode 100644 index 4afc13a0d5..0000000000 --- a/data/core.telegram.org/method/messages.uninstallStickerSet +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.uninstallStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

messages.uninstallStickerSet

- -

Uninstall a stickerset

-

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetThe stickerset to uninstall
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.updateDialogFiltersOrder b/data/core.telegram.org/method/messages.updateDialogFiltersOrder deleted file mode 100644 index 0bdf4b992d..0000000000 --- a/data/core.telegram.org/method/messages.updateDialogFiltersOrder +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.updateDialogFiltersOrder - - - - - - - - - - - - - -
- -
-
-
- -

messages.updateDialogFiltersOrder

- -

Reorder folders

-

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
orderVector<int>New folder order
-

Result

-

Bool

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/payments.getBankCardData b/data/core.telegram.org/method/payments.getBankCardData deleted file mode 100644 index eb98dd017f..0000000000 --- a/data/core.telegram.org/method/payments.getBankCardData +++ /dev/null @@ -1,149 +0,0 @@ - - - - - payments.getBankCardData - - - - - - - - - - - - - -
- -
-
-
- -

payments.getBankCardData

- -

Get info about a credit card

-

-
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
----functions---
-payments.getBankCardData#2e79d779 number:string = payments.BankCardData;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
numberstringCredit card number
-

Result

-

payments.BankCardData

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.getCallConfig b/data/core.telegram.org/method/phone.getCallConfig deleted file mode 100644 index 146a1249c9..0000000000 --- a/data/core.telegram.org/method/phone.getCallConfig +++ /dev/null @@ -1,134 +0,0 @@ - - - - - phone.getCallConfig - - - - - - - - - - - - - -
- -
-
-
- -

phone.getCallConfig

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.saveCallDebug b/data/core.telegram.org/method/phone.saveCallDebug deleted file mode 100644 index 3a5342f7bb..0000000000 --- a/data/core.telegram.org/method/phone.saveCallDebug +++ /dev/null @@ -1,177 +0,0 @@ - - - - - phone.saveCallDebug - - - - - - - - - - - - - -
- -
-
-
- -

phone.saveCallDebug

- -

Send phone call debug data to server

-

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPhoneCallPhone call
debugDataJSONDebug statistics obtained from libtgvoip
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_PEER_INVALIDThe provided call peer object is invalid
400DATA_JSON_INVALIDThe provided JSON data is invalid
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/photos.deletePhotos b/data/core.telegram.org/method/photos.deletePhotos deleted file mode 100644 index 54a646100e..0000000000 --- a/data/core.telegram.org/method/photos.deletePhotos +++ /dev/null @@ -1,148 +0,0 @@ - - - - - photos.deletePhotos - - - - - - - - - - - - - -
- -
-
-
- -

photos.deletePhotos

- -

Deletes profile photos.

-

-
---functions---
-photos.deletePhotos#87cf7f2f id:Vector<InputPhoto> = Vector<long>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<InputPhoto>Input photos to delete
-

Result

-

Method returns a list of successfully deleted photos in Vector<long>

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stats.getMegagroupStats b/data/core.telegram.org/method/stats.getMegagroupStats deleted file mode 100644 index 8df2f8d812..0000000000 --- a/data/core.telegram.org/method/stats.getMegagroupStats +++ /dev/null @@ -1,165 +0,0 @@ - - - - - stats.getMegagroupStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.getMegagroupStats

- -

Get supergroup statistics

-

-
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
----functions---
-stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelSupergroup ID
-

Result

-

stats.MegagroupStats

-

Bots can use this method

-

Related pages

-

Channels

-

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

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stats.getMessagePublicForwards b/data/core.telegram.org/method/stats.getMessagePublicForwards deleted file mode 100644 index 7608717c0f..0000000000 --- a/data/core.telegram.org/method/stats.getMessagePublicForwards +++ /dev/null @@ -1,208 +0,0 @@ - - - - - stats.getMessagePublicForwards - - - - - - - - - - - - - -
- -
-
-
- -

stats.getMessagePublicForwards

- -

Obtains a list of messages, indicating to which other public channels was a channel message forwarded.
-Will return a list of messages with peer_id equal to the public channel to which this message was forwarded.

-

-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-stats.getMessagePublicForwards#5630281b channel:InputChannel msg_id:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelSource channel
msg_idintSource message ID
offset_rateintInitially 0, then set to the next_rate parameter of messages.messagesSlice
offset_peerInputPeerOffsets for pagination, for more info click here
offset_idintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid
400MESSAGE_ID_INVALIDThe provided message id is invalid
-

Bots can use this method

-

Related pages

-

messages.messagesSlice

-

Incomplete list of messages and auxiliary data.

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

message

-

A message

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/methods.html b/data/core.telegram.org/methods.html deleted file mode 100644 index bfde4f831a..0000000000 --- a/data/core.telegram.org/methods.html +++ /dev/null @@ -1,2084 +0,0 @@ - - - - - Methods - - - - - - - - - - - - - -
- -
-
-
- -

Methods

- -

Accepting the Terms of Service

- - - - - - - - - - - - - - - - - -
NameDescription
help.getTermsOfServiceUpdateLook for updates of telegram's terms of service
help.acceptTermsOfServiceAccept the new terms of service
-

Dealing with spam and ToS violations

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.reportPeerReport a peer for violation of telegram's Terms of Service
channels.reportSpamReports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup
messages.reportReport a message in a chat for violation of telegram's Terms of Service
messages.reportSpamReport a new incoming chat for spam, if the peer settings of the chat allow us to do that
messages.reportEncryptedSpamReport a secret chat for spam
-

Fetching configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
help.getAppChangelogGet changelog of current app.
Typically, an updates constructor will be returned, containing one or more updateServiceNotification updates with app-specific changelogs.
help.getAppConfigGet app-specific configuration, see client configuration for more info on the result.
help.getAppUpdateReturns information on update availability for the current application.
help.getConfigReturns current configuration, including data center configuration.
help.getInviteTextReturns localized text of a text message with an invitation.
help.getNearestDcReturns info on data centre nearest to the user.
help.getSupportReturns the support user for the 'ask a question' feature.
help.getSupportNameGet localized name of the telegram support user
help.getCountriesListGet name, ISO code, localized name and phone codes/patterns of all available countries
help.dismissSuggestionDismiss a suggestion
-

Login via QR code

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
auth.exportLoginTokenGenerate a login token, for login via QR code.
The generated login token should be encoded using base64url, then shown as a tg://login?token=base64encodedtoken URL in the QR code.

For more info, see login via QR code.
auth.acceptLoginTokenAccept QR code login token, logging in the app that generated it.

Returns info about the new session.

For more info, see login via QR code.
auth.importLoginTokenLogin using a redirected login token, generated in case of DC mismatch during QR code login.

For more info, see login via QR code.
-

Miscellaneous

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
help.saveAppLogSaves logs of application on the server.
initConnectionInitialize connection
invokeAfterMsgInvokes a query after successfull completion of one of the previous queries.
invokeAfterMsgsInvokes a query after a successfull completion of previous queries
invokeWithLayerInvoke the specified query using the specified API layer
invokeWithoutUpdatesInvoke a request without subscribing the used connection for updates (this is enabled by default for file queries).
-

Registration/Authorization

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
auth.bindTempAuthKeyBinds a temporary authorization key temp_auth_key_id to the permanent authorization key perm_auth_key_id. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

For more information, see Perfect Forward Secrecy.
auth.cancelCodeCancel the login verification code
auth.checkPasswordTry logging to an account protected by a 2FA password.
auth.dropTempAuthKeysDelete all temporary authorization keys except for the ones specified
auth.exportAuthorizationReturns data for copying authorization to another data-centre.
auth.importAuthorizationLogs in a user using a key transmitted from his native data-centre.
auth.importBotAuthorizationLogin as a bot
auth.logOutLogs out the user.
auth.recoverPasswordReset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.
auth.requestPasswordRecoveryRequest recovery code of a 2FA password, only for accounts with a recovery email configured.
auth.resendCodeResend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.
auth.resetAuthorizationsTerminates all user's authorized sessions except for the current one.

After calling this method it is necessary to reregister the current device using the method account.registerDevice
auth.sendCodeSend the verification code for login
auth.signInSigns in a user with a validated phone number.
auth.signUpRegisters a validated phone number in the system.
-

Working with GDPR export

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.initTakeoutSessionIntialize account takeout session
account.finishTakeoutSessionFinish account takeout session
messages.getSplitRangesGet message ranges for saving the user's chat history
channels.getLeftChannelsGet a list of channels/supergroups we left
invokeWithMessagesRangeInvoke with the given message range
invokeWithTakeoutInvoke a method within a takeout session
-

Working with GIFs (actually MPEG4 GIFs)

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getSavedGifsGet saved GIFs
messages.saveGifAdd GIF to saved gifs list
messages.searchGifsSearch for GIFs
-

Working with Public Service Announcement and MTProxy channels

- - - - - - - - - - - - - - - - - -
NameDescription
help.hidePromoDataHide MTProxy/Public Service Announcement information
help.getPromoDataGet MTProxy/Public Service Announcement information
-

Working with TSF (internal use only)

- - - - - - - - - - - - - - - - - -
NameDescription
help.editUserInfoInternal use
help.getUserInfoInternal use
-

Working with 2FA login

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.confirmPasswordEmailVerify an email to use as 2FA recovery method.
account.resendPasswordEmailResend the code to verify an email to use as 2FA recovery method.
account.cancelPasswordEmailCancel the code that was sent to verify an email to use as 2FA recovery method.
account.getPasswordObtain configuration for two-factor authorization with password
account.getPasswordSettingsGet private info associated to the password info (recovery email, telegram passport info & so on)
account.updatePasswordSettingsSet a new 2FA password
-

Working with Seamless Telegram Login

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.requestUrlAuthGet more info about a Seamless Telegram Login authorization request, for more info click here »
messages.acceptUrlAuthUse this to accept a Seamless Telegram Login authorization request, for more info click here »
account.getWebAuthorizationsGet web login widget authorizations
account.resetWebAuthorizationLog out an active web telegram login session
account.resetWebAuthorizationsReset all active web telegram login sessions
-

Working with VoIP calls

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
phone.acceptCallAccept incoming call
phone.confirmCallComplete phone call E2E encryption key exchange »
phone.discardCallRefuse or end running call
phone.getCallConfigGet phone call configuration to be passed to libtgvoip's shared config
phone.receivedCallOptional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.
phone.requestCallStart a telegram phone call
phone.saveCallDebugSend phone call debug data to server
phone.sendSignalingDataSend VoIP signaling data
phone.setCallRatingRate a call
-

Working with channels/supergroups/geogroups

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
channels.createChannelCreate a supergroup/channel.
channels.getInactiveChannelsGet inactive channels and supergroups
channels.deleteChannelDelete a channel/supergroup
channels.deleteHistoryDelete the history of a supergroup
channels.deleteMessagesDelete messages in a channel/supergroup
channels.deleteUserHistoryDelete all messages sent by a certain user in a supergroup
channels.editAdminModify the admin rights of a user in a supergroup/channel.
channels.editBannedBan/unban/kick a user in a supergroup/channel.
channels.editCreatorTransfer channel ownership
channels.editLocationEdit location of geogroup
channels.editPhotoChange the photo of a channel/supergroup
channels.editTitleEdit the name of a channel/supergroup
channels.exportMessageLinkGet link and embed info of a message in a channel/supergroup
channels.getAdminLogGet the admin log of a channel/supergroup
channels.getAdminedPublicChannelsGet channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.
channels.getChannelsGet info about channels/supergroups
channels.getFullChannelGet full info about a channel
channels.getGroupsForDiscussionGet all groups that can be used as discussion groups.

Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first.
channels.getMessagesGet channel/supergroup messages
channels.getParticipantGet info about a channel/supergroup participant
channels.getParticipantsGet the participants of a supergroup/channel
channels.inviteToChannelInvite users to a channel/supergroup
channels.joinChannelJoin a channel/supergroup
channels.leaveChannelLeave a channel/supergroup
channels.readHistoryMark channel/supergroup history as read
channels.readMessageContentsMark channel/supergroup message contents as read
channels.setDiscussionGroupAssociate a group to a channel as discussion group for that channel
channels.setStickersAssociate a stickerset to the supergroup
channels.togglePreHistoryHiddenHide/unhide message history for new channel/supergroup users
channels.toggleSignaturesEnable/disable message signatures in channels
channels.toggleSlowModeToggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds
messages.getStatsURLReturns URL with the chat statistics. Currently this method can be used only for channels
-

Working with chats/supergroups/channels

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.addChatUserAdds a user to a chat and sends a service message on it.
messages.checkChatInviteCheck the validity of a chat invite link and get basic info about it
messages.createChatCreates a new chat.
messages.deleteChatUserDeletes a user from a chat and sends a service message on it.
messages.editChatAboutEdit the description of a group/supergroup/channel.
messages.editChatAdminMake a user admin in a legacy group.
messages.editChatDefaultBannedRightsEdit the default banned rights of a channel/supergroup/group.
messages.editChatPhotoChanges chat photo and sends a service message on it
messages.editChatTitleChanages chat name and sends a service message on it.
messages.exportChatInviteExport an invite link for a chat
messages.getAllChatsGet all chats, channels and supergroups
messages.getChatsReturns chat basic info on their IDs.
messages.getCommonChatsGet chats in common with a user
messages.getFullChatReturns full chat info according to its ID.
messages.importChatInviteImport a chat invite and join a private chat/supergroup/channel
messages.migrateChatTurn a legacy group into a supergroup
-

Working with deep links

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.startBotStart a conversation with a bot using a deep linking parameter
help.getDeepLinkInfoGet info about a t.me link
help.getRecentMeUrlsGet recently used t.me links
-

Working with files

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
help.getCdnConfigGet configuration for CDN file downloads.
upload.getCdnFileDownload a CDN file.
upload.getCdnFileHashesGet SHA256 hashes for verifying downloaded CDN files
upload.reuploadCdnFileRequest a reupload of a certain file to a CDN DC.
upload.getFileReturns content of a whole file or its part.
upload.getFileHashesGet SHA256 hashes for verifying downloaded files
upload.getWebFileReturns content of an HTTP file or a part, by proxying the request through telegram.
upload.saveBigFilePartSaves a part of a large file (over 10Mb in size) to be later passed to one of the methods.
upload.saveFilePartSaves a part of file for futher sending to one of the methods.
messages.uploadEncryptedFileUpload encrypted file and associate it to a secret chat
messages.uploadMediaUpload a file and associate it to a chat (without actually sending it to the chat)
messages.getDocumentByHashGet a document by its SHA256 hash, mainly used for gifs
-

Working with instant view pages

- - - - - - - - - - - - - - - - - -
NameDescription
messages.getWebPageGet instant view page
messages.getWebPagePreviewGet preview of webpage
-

Working with secret chats

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.setEncryptedTypingSend typing event by the current user to a secret chat.
messages.readEncryptedHistoryMarks message history within a secret chat as read.
messages.acceptEncryptionConfirms creation of a secret chat
messages.discardEncryptionCancels a request for creation and/or delete info on secret chat.
messages.requestEncryptionSends a request to start a secret chat to the user.
messages.sendEncryptedSends a text message to a secret chat.
messages.sendEncryptedFileSends a message with a file attachment to a secret chat
messages.sendEncryptedServiceSends a service message to a secret chat.
messages.getDhConfigReturns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.
messages.receivedQueueConfirms receipt of messages in a secret chat by client, cancels push notifications.
-

Working with telegram passport

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.sendVerifyEmailCodeSend the verification email code for telegram passport.
account.verifyEmailVerify an email address for telegram passport.
account.sendVerifyPhoneCodeSend the verification phone code for telegram passport.
account.verifyPhoneVerify a phone number for telegram passport.
account.acceptAuthorizationSends a Telegram Passport authorization form, effectively sharing data with the service
account.getAuthorizationFormReturns a Telegram Passport authorization form for sharing data with a service
account.getAuthorizationsGet logged-in sessions
account.deleteSecureValueDelete stored Telegram Passport documents, for more info see the passport docs »
account.getAllSecureValuesGet all saved Telegram Passport documents, for more info see the passport docs »
account.getSecureValueGet saved Telegram Passport document, for more info see the passport docs »
account.saveSecureValueSecurely save Telegram Passport document, for more info see the passport docs »
help.getPassportConfigGet passport configuration
users.setSecureValueErrorsNotify the user that the sent passport data contains some errors The user will not be able to re-submit their Passport data to you until the errors are fixed (the contents of the field for which you returned the error must change).

Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.
-

Working with updates

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
updates.getChannelDifferenceReturns the difference between the current state of updates of a certain channel and transmitted.
updates.getDifferenceGet new updates.
updates.getStateReturns a current state of updates.
-

Working with bot inline queries and callback buttons

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getInlineBotResultsQuery an inline bot
messages.setInlineBotResultsAnswer an inline query, for bots only
messages.sendInlineBotResultSend a result obtained using messages.getInlineBotResults.
messages.getBotCallbackAnswerPress an inline callback button and get a callback answer from the bot
messages.setBotCallbackAnswerSet the callback answer to a user button press (bots only)
messages.editInlineBotMessageEdit an inline bot message
-

Working with bots

- - - - - - - - - - - - - -
NameDescription
bots.setBotCommandsSet bot command list
-

Working with bots (internal bot API use)

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
bots.answerWebhookJSONQueryAnswers a custom query; for bots only
bots.sendCustomRequestSends a custom request; for bots only
help.setBotUpdatesStatusInforms the server about the number of pending bot updates if they haven't been processed for a long time; for bots only
-

Working with cloud themes

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.updateThemeUpdate theme
account.uploadThemeUpload theme
account.getThemesGet installed themes
account.createThemeCreate a theme
account.installThemeInstall a theme
account.saveThemeSave a theme
account.getThemeGet theme information
-

Working with contacts and top peers

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.getContactSignUpNotificationWhether the user will receive notifications when contacts sign up
account.setContactSignUpNotificationToggle contact sign up notifications
contacts.acceptContactIf the peer settings of a new user allow us to add him as contact, add that user as contact
contacts.addContactAdd an existing telegram user as contact.

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.
contacts.blockAdds the user to the blacklist.
contacts.deleteByPhonesDelete contacts by phone number
contacts.deleteContactsDeletes several contacts from the list.
contacts.getBlockedReturns the list of blocked users.
contacts.getContactIDsGet contact by telegram IDs
contacts.getContactsReturns the current user's contact list.
contacts.getLocatedGet contacts near you
contacts.getSavedGet all contacts
contacts.getStatusesReturns the list of contact statuses.
contacts.getTopPeersGet most used peers
contacts.importContactsImports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

Use contacts.addContact to add Telegram contacts without actually using their phone number.
contacts.resetSavedDelete saved contacts
contacts.resetTopPeerRatingReset rating of top peer
contacts.searchReturns users found by username substring.
contacts.toggleTopPeersEnable/disable top peers
contacts.unblockDeletes the user from the blacklist.
-

Working with credit cards

- - - - - - - - - - - - - -
NameDescription
payments.getBankCardDataGet info about a credit card
-

Working with dialogs

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getDialogsReturns the current user dialog list.
messages.getPeerDialogsGet dialog info of specified peers
messages.getPinnedDialogsGet pinned dialogs
messages.toggleDialogPinPin/unpin a dialog
messages.reorderPinnedDialogsReorder pinned dialogs
messages.getDialogUnreadMarksGet dialogs manually marked as unread
messages.markDialogUnreadManually mark dialog as unread
messages.getPeerSettingsGet peer settings
messages.hidePeerSettingsBarShould be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.
messages.getOnlinesGet count of online users in a chat
messages.sendScreenshotNotificationNotify the other user in a private chat that a screenshot of the chat was taken
messages.setTypingSends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.
-

Working with drafts

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.clearAllDraftsClear all drafts.
messages.getAllDraftsSave get all message drafts.
messages.saveDraftSave a message draft associated to a chat.
-

Working with emoji keywords

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getEmojiKeywordsGet localized emoji keywords
messages.getEmojiKeywordsDifferenceGet changed emoji keywords
messages.getEmojiKeywordsLanguagesGet info about an emoji keyword localization
messages.getEmojiURLReturns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
-

Working with folders

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.updateDialogFiltersOrderReorder folders
messages.getDialogFiltersGet folders
messages.getSuggestedDialogFiltersGet suggested folders
messages.updateDialogFilterUpdate folder
folders.deleteFolderDelete a peer folder
folders.editPeerFoldersEdit peers in peer folder
-

Working with games

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getGameHighScoresGet highscores of a game
messages.getInlineGameHighScoresGet highscores of a game sent using an inline bot
messages.setGameScoreUse this method to set the score of the specified user in a game sent as a normal message (bots only).
messages.setInlineGameScoreUse this method to set the score of the specified user in a game sent as an inline message (bots only).
-

Working with localization packs

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
langpack.getDifferenceGet new strings in languagepack
langpack.getLangPackGet localization pack strings
langpack.getLanguageGet information about a language in a localization pack
langpack.getLanguagesGet information about all languages in a localization pack
langpack.getStringsGet strings from a language pack
-

Working with media autodownload settings

- - - - - - - - - - - - - - - - - -
NameDescription
account.getAutoDownloadSettingsGet media autodownload settings
account.saveAutoDownloadSettingsChange media autodownload settings
-

Working with message threads

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getRepliesGet messages in a reply thread
contacts.blockFromRepliesStop getting notifications about thread replies of a certain user in @replies
messages.getDiscussionMessageGet discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group
messages.readDiscussionMark a thread as read
-

Working with message reactions

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getMessagesReactionsGet message reactions
messages.sendReactionSend reaction to message
messages.getMessageReactionsListGet full message reaction list
-

Working with messages

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.deleteHistoryDeletes communication history.
messages.deleteMessagesDeletes messages by their identifiers.
messages.editMessageEdit message
messages.forwardMessagesForwards messages by their IDs.
messages.getHistoryGets back the conversation history with one interlocutor / within a chat
messages.getMessageEditDataFind out if a media message's caption can be edited
messages.getMessagesReturns the list of messages by their IDs.
messages.getMessagesViewsGet and increase the view counter of a message sent or forwarded from a channel
messages.getRecentLocationsGet live location history of a certain user
messages.getSearchCountersGet the number of results that would be found by a messages.search call with the same parameters
messages.getUnreadMentionsGet unread messages where we were mentioned
messages.readHistoryMarks message history as read.
messages.readMentionsMark mentions as read
messages.readMessageContentsNotifies the sender about the recipient having listened a voice message or watched a video.
messages.receivedMessagesConfirms receipt of messages by a client, cancels PUSH-notification sending.
messages.searchGets back found messages
messages.searchGlobalSearch for messages and peers globally
messages.sendMediaSend a media
messages.sendMessageSends a message to a chat
messages.sendMultiMediaSend an album or grouped media
messages.updatePinnedMessagePin a message
messages.unpinAllMessagesUnpin all pinned messages
-

Working with notification settings

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.registerDeviceRegister device to receive PUSH notifications
account.unregisterDeviceDeletes a device by its token, stops sending PUSH-notifications to it.
account.updateDeviceLockedWhen client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.
account.getNotifyExceptionsReturns list of chats with non-default notification settings
account.getNotifySettingsGets current notification settings for a given user/group, from all users/all groups.
account.updateNotifySettingsEdits notification settings from a given user/group, from all users/all groups.
account.resetNotifySettingsResets all notification settings from users and groups.
-

Working with other users

- - - - - - - - - - - - - - - - - -
NameDescription
users.getFullUserReturns extended user info by ID.
users.getUsersReturns basic user info according to their identifiers.
-

Working with payments

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
payments.getSavedInfoGet saved payment information
payments.clearSavedInfoClear saved payment information
payments.getPaymentFormGet a payment form
payments.validateRequestedInfoSubmit requested order information for validation
messages.setBotShippingResultsIf you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.
account.getTmpPasswordGet temporary payment password
payments.sendPaymentFormSend compiled payment form
messages.setBotPrecheckoutResultsOnce the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery update.
Use this method to respond to such pre-checkout queries.
Note: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.
payments.getPaymentReceiptGet payment receipt
-

Working with polls

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getPollResultsGet poll results
messages.getPollVotesGet poll results for non-anonymous polls
messages.sendVoteVote in a poll
-

Working with scheduled messages

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.sendScheduledMessagesSend scheduled messages right away
messages.getScheduledHistoryGet scheduled messages
messages.deleteScheduledMessagesDelete scheduled messages
messages.getScheduledMessagesGet scheduled messages
-

Working with sensitive content (NSFW)

- - - - - - - - - - - - - - - - - -
NameDescription
account.getContentSettingsGet sensitive content settings
account.setContentSettingsSet sensitive content settings (for viewing or hiding NSFW content)
-

Working with sponsored proxies

- - - - - - - - - - - - - -
NameDescription
help.getProxyDataGet promotion info of the currently-used MTProxy
-

Working with statistics

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
stats.loadAsyncGraphLoad channel statistics graph asynchronously
stats.getBroadcastStatsGet channel statistics
stats.getMessagePublicForwardsObtains a list of messages, indicating to which other public channels was a channel message forwarded.
Will return a list of messages with peer_id equal to the public channel to which this message was forwarded.
stats.getMegagroupStatsGet supergroup statistics
stats.getMessageStatsGet message statistics
-

Working with stickers

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getOldFeaturedStickersMethod for fetching previously featured stickers
messages.toggleStickerSetsApply changes to multiple stickersets
stickers.setStickerSetThumbSet stickerset thumbnail
stickers.addStickerToSetAdd a sticker to a stickerset, bots only. The sticker set must have been created by the bot.
stickers.changeStickerPositionChanges the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot
stickers.createStickerSetCreate a stickerset, bots only.
stickers.removeStickerFromSetRemove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.
messages.clearRecentStickersClear recent stickers
messages.faveStickerMark a sticker as favorite
messages.getAllStickersGet all installed stickers
messages.getArchivedStickersGet all archived stickers
messages.getAttachedStickersGet stickers attached to a photo or video
messages.getFavedStickersGet faved stickers
messages.getFeaturedStickersGet featured stickers
messages.getMaskStickersGet installed mask stickers
messages.getRecentStickersGet recent stickers
messages.getStickerSetGet info about a stickerset
messages.getStickersGet stickers by emoji
messages.saveRecentStickerAdd/remove sticker from recent stickers list
messages.installStickerSetInstall a stickerset
messages.readFeaturedStickersMark new featured stickers as read
messages.reorderStickerSetsReorder installed stickersets
messages.searchStickerSetsSearch for stickersets
messages.uninstallStickerSetUninstall a stickerset
-

Working with the user's account

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.changePhoneChange the phone number of the current account
account.confirmPhoneConfirm a phone number to cancel account deletion, for more info click here »
account.deleteAccountDelete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.
account.getAccountTTLGet days to live of account
account.getPrivacyGet privacy settings of current account
account.resetAuthorizationLog out an active authorized session by its hash
account.sendChangePhoneCodeVerify a new phone number to associate to the current account
account.sendConfirmPhoneCodeSend confirmation code to cancel account deletion, for more info click here »
account.setAccountTTLSet account self-destruction period
account.setPrivacyChange privacy settings of current account
account.setGlobalPrivacySettingsSet global privacy settings
account.getGlobalPrivacySettingsGet global privacy settings
account.updateProfileUpdates user profile.
account.updateStatusUpdates online user status.
-

Working with user profile pictures

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
photos.deletePhotosDeletes profile photos.
photos.getUserPhotosReturns the list of user photos.
photos.updateProfilePhotoInstalls a previously uploaded photo as a profile photo.
photos.uploadProfilePhotoUpdates current user profile photo.
-

Working with usernames

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
channels.checkUsernameCheck if a username is free and can be assigned to a channel/supergroup
channels.updateUsernameChange the username of a supergroup/channel
account.updateUsernameChanges username for the current user.
account.checkUsernameValidates a username and checks availability.
contacts.resolveUsernameResolve a @username to get peer info
-

Working with wallpapers

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.getMultiWallPapersGet info about multiple wallpapers
account.getWallPaperGet info about a certain wallpaper
account.getWallPapersReturns a list of available wallpapers.
account.installWallPaperInstall wallpaper
account.resetWallPapersDelete installed wallpapers
account.saveWallPaperInstall/uninstall wallpaper
account.uploadWallPaperCreate and upload a new wallpaper
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/TL-types.html b/data/core.telegram.org/mtproto/TL-types.html deleted file mode 100644 index cdab6154d1..0000000000 --- a/data/core.telegram.org/mtproto/TL-types.html +++ /dev/null @@ -1,124 +0,0 @@ - - - - - Type serialization - - - - - - - - - - - - - -
- -
-
-
- -

Type serialization

- -

See Polymorphism in TL and TL Language.

-

It remains to describe how types, e.g. values of type Type, are transmitted (serialized). In general, there is nothing unexpected going on here: we have type constructors of various arities (for example, List is an arity-1 constructor, but IntList is a 0-arity constructor); and if we know that a 32-bit “name” is assigned to each type constructor, there are no further questions -- values of type Type are serialized exactly like values of any other recursive type with a defined set of constructors of differing arity.

-

How can a 32-bit “name” be assigned to a type (a type constructor, to be more exact) such as List or IntList? -It is proposed to use the sum of the names of all of its constructors, plus the CRC32 of the string with the designation of the type's name and all of its parameters such as “IntList = Type” or “List X:Type = Type”. This way, the List constructor’s “name” is the sum of the CRC32s of the three strings "List X:Type = Type", "cons X:Type hd:X tl:List X = List X", and "nil X:Type = List X". -For “bare” types (which, formally speaking, are subtypes of the corresponding “boxed” type), the situation is somewhat more complicated; the logical negation of the corresponding constructor’s name is used. For built-in bareand boxed types (for example, int and Int), a pseudo-declaration is used (for example, int ? = Int").

-
    -
  • This description is somewhat outdated and may be updated in the future. Specifically, how to treat the ! modifier has not been explained.*
  • -
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto_v1.html b/data/core.telegram.org/mtproto_v1.html deleted file mode 100644 index d395ad3347..0000000000 --- a/data/core.telegram.org/mtproto_v1.html +++ /dev/null @@ -1,229 +0,0 @@ - - - - - MTProto Mobile Protocol v.1.0 (DEPRECATED) - - - - - - - - - - - - - -
- -
-
-
-
-

MTProto Mobile Protocol v.1.0 (DEPRECATED)

- -
-

This document describes MTProto v1.0, its status is DEPRECATED.
For information on encryption used in up-to-date Telegram clients, kindly see this document.

-
-

Related articles

-

-
-

This page deals with the basic layer of MTProto encryption used for Cloud chats (server-client encryption). See also:

- -

General Description

-

The protocol is designed for access to a server API from applications running on mobile devices. It must be emphasized that a web browser is not such an application.

-

The protocol is subdivided into three virtually independent components:

-
    -
  • High-level component (API query language): defines the method whereby API queries and responses are converted to binary messages.
  • -
  • Cryptographic (authorization) layer: defines the method by which messages are encrypted prior to being transmitted through the transport protocol.
  • -
  • Transport component: defines the method for the client and the server to transmit messages over some other existing network protocol (such as, http, https, tcp, udp).
  • -
- - -
-

Got questions about this setup? — Check out the Advanced FAQ!

-
-
Note 1
-

Each plaintext message to be encrypted in MTProto always contains the following data to be checked upon decryption in order to make the system robust against known problems with the components:

-
    -
  • server salt (64-Bit)
  • -
  • session id
  • -
  • message sequence number
  • -
  • message length
  • -
  • time
  • -
-
Note 2
-

See additional comments on our use of IGE, SHA-1 and message authentication.

-
Note 3
-

Telegram's End-to-end encrypted Secret Chats are using an additional layer of encryption on top of the described above. See Secret Chats, End-to-End encryption for details.

-

Brief Component Summary

-

High-Level Component (RPC Query Language/API)

-

From the standpoint of the high-level component, the client and the server exchange messages inside a session. The session is attached to the client device (the application, to be more exact) rather than a specific http/https/tcp connection. In addition, each session is attached to a user key ID by which authorization is actually accomplished.

-

Several connections to a server may be open; messages may be sent in either direction through any of the connections (a response to a query is not necessarily returned through the same connection that carried the original query, although most often, that is the case; however, in no case can a message be returned through a connection belonging to a different session). When the UDP protocol is used, a response might be returned by a different IP address than the one to which the query had been sent.

-

There are several types of messages:

-
    -
  • RPC calls (client to server): calls to API methods
  • -
  • RPC responses (server to client): results of RPC calls
  • -
  • Message received acknowledgment (or rather, notification of status of a set of messages)
  • -
  • Message status query
  • -
  • Multipart message or container (a container that holds several messages; needed to send several RPC calls at once over an HTTP connection, for example; also, a container may support gzip).
  • -
-

From the standpoint of lower level protocols, a message is a binary data stream aligned along a 4 or 16-byte boundary. The first several fields in the message are fixed and are used by the cryptographic/authorization system.

-

Each message, either individual or inside a container, consists of a message identifier (64 bits, see below), a message sequence number within a session (32 bits), the length (of the message body in bytes; 32 bits), and a body (any size which is a multiple of 4 bytes). In addition, when a container or a single message is sent, an internal header is added at the top (see below), then the entire message is encrypted, and an external header is placed at the top of the message (a 64-bit key identifier and a 128-bit message key).

-

A message body normally consists of a 32-bit message type followed by type-dependent parameters. In particular, each RPC function has a corresponding message type. For more detail, see Binary Data Serialization, Mobile Protocol: Service Messages.

-

All numbers are written as little endian. However, very large numbers (2048-bit) used in RSA and DH are written in the big endian format because that is what the OpenSSL library does.

-

Authorization and Encryption

-

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key. A user key together with the message key defines an actual 256-bit key which is what encrypts the message using AES-256 encryption. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 lower-order bits of the SHA1 of the message body (including session, message ID, etc.). Multipart messages are encrypted as a single message.

-

For a technical specification, see Mobile Protocol: Detailed Description
The first thing a client application must do is create an authorization key which is normally generated when it is first run and almost never changes.

-

The protocol’s principal drawback is that an intruder passively intercepting messages and then somehow appropriating the authorization key (for example, by stealing a device) will be able to decrypt all the intercepted messages post factum. This probably is not too much of a problem (by stealing a device, one could also gain access to all the information cached on the device without decrypting anything); however, the following steps could be taken to overcome this weakness:

-
    -
  • Session keys generated using the Diffie-Hellman protocol and used in conjunction with the authorization and the message keys to select AES parameters. To create these, the first thing a client must do after creating a new session is send a special RPC query to the server (“generate session key”) to which the server will respond, whereupon all subsequent messages within the session are encrypted using the session key as well.
  • -
  • Protecting the key stored on the client device with a (text) password; this password is never stored in memory and is entered by a user when starting the application or more frequently (depending on application settings).
  • -
  • Data stored (cached) on the user device can also be protected by encryption using an authorization key which, in turn, is to be password-protected. Then, a password will be required to gain access even to those data.
  • -
-

Time Synchronization

-

If client time diverges widely from server time, a server may start ignoring client messages, or vice versa, because of an invalid message identifier (which is closely related to creation time). Under these circumstances, the server will send the client a special message containing the correct time and a certain 128-bit salt (either explicitly provided by the client in a special RPC synchronization request or equal to the key of the latest message received from the client during the current session). This message could be the first one in a container that includes other messages (if the time discrepancy is significant but does not as yet result in the client’s messages being ignored).

-

Having received such a message or a container holding it, the client first performs a time synchronization (in effect, simply storing the difference between the server’s time and its own to be able to compute the “correct” time in the future) and then verifies that the message identifiers for correctness.

-

Where a correction has been neglected, the client will have to generate a new session to assure the monotonicity of message identifiers.

-

Transport

-

Enables the delivery of encrypted containers together with the external header (hereinafter, Payload) from client to server and back. There are three types of transport:

-
    -
  • HTTP
  • -
  • TCP
  • -
  • UDP
  • -
-

We shall examine the first two types.

-

HTTP Transport

-

Implemented over HTTP/1.1 (with keepalive) running over the traditional TCP Port 80. HTTPS is not used; the above encryption method is used instead.

-

An HTTP connection is attached to a session (or rather, to session + key identifier) specified in the most recent user query received; normally, the session is the same in all queries, but crafty HTTP proxies may corrupt that. A server may not return a message into an HTTP connection unless it belongs to the same session, and unless it is the server’s turn (an HTTP request had been received from the client to which a response has not been sent yet).

-

The overall arrangement is as follows. The client opens one or more keepalive HTTP connections to the server. If one or more messages need to be sent, they are made into a payload which is followed by a POST request to the URL/api to which the payload is transmitted as data. In addition, Content-Length, Keepalive, and Host are valid HTTP headers.

-

Having received the query, the server may either wait a little while (if the query requires a response following a short timeout) or immediately return a dummy response (only acknowledging the receipt of the container). In any case, the response may contain any number of messages. The server may at the same time send out any other messages it might be holding for the session.

-

In addition, there exists a special long poll RPC query (valid for HTTP connections only) which transmits maximum timeout T. If the server has messages for the session, they are returned immediately; otherwise, a wait state is entered until such time as the server has a message for the client or T seconds have elapsed. If no events occur in the span of T seconds, a dummy response is returned (special message).

-

If a server needs to send a message to a client, it checks for an HTTP connection that belongs to the required session and is in the “answering an HTTP request” state (including long poll) whereupon the message is added to the response container for the connection and sent to the user. In a typical case, there is some additional wait time (50 milliseconds) against the eventuality that the server will soon have more messages for the session.

-

If no suitable HTTP connection is available, the messages are placed in the current session’s send queue. However, they find their way there anyway until receipt is explicitly or indirectly confirmed by the client. For the HTTP protocol, sending the next query into the same HTTP connection is regarded as an implicit acknowledgment (not any more, the HTTP protocol also requires that explicit acknowledgments be sent); in other cases, the client must return an explicit acknowledgment within a reasonable time (it can be added to a container for the following request).

-

Important: if the acknowledgment fails to arrive on time, the message can be resent (possibly, in a different container). The parties must autonomously be ready for this and must store the identifiers of the most recent messages received (and ignore such duplicates rather than repeat actions). In order not to have the identifiers stored forever, there exist special garbage collection messages that take advantage of message identifier monotonicity.

-

If the send queue overflows or if messages stay in the queue for over 10 minutes, the server forgets them (or sends them to swap, no genius required). This may happen even faster, if the server is running out of buffer space (for example, because of serious network issues resulting in a large number of connections becoming severed).

-

TCP Transport

-

This is very similar to the HTTP transport. May also be implemented over Port 80 (to penetrate all firewalls) and even use the same server IP addresses. In this situation, the server understands whether HTTP or TCP protocol must be used for the connection, based on the first four incoming bytes (for HTTP, it is POST).

-

When a TCP connection is created, it is assigned to the session (and the authorization key) transmitted in the first user message, and subsequently used exclusively for this session (multiplexing arrangements are not allowed).

-

If a payload (packet) needs to be transmitted from server to client or from client to server, it is encapsulated as follows: 4 length bytes are added at the front (to include the length, the sequence number, and CRC32; always divisible by 4) and 4 bytes with the packet sequence number within this TCP connection (the first packet sent is numbered 0, the next one 1, etc.), and 4 CRC32 bytes at the end (length, sequence number, and payload together).

-

There is an abridged version of the same protocol: if the client sends 0xef as the first byte (important: only prior to the very first data packet), then packet length is encoded by a single byte (0x01..0x7e = data length divided by 4; or 0x7f followed by 3 length bytes (little endian) divided by 4) followed by the data themselves (sequence number and CRC32 not added). In this case, server responses look the same (the server does not send 0xefas the first byte).

-

In case 4-byte data alignment is needed, an intermediate version of the original protocol may be used: if the client sends 0xeeeeeeee as the first int (four bytes), then packet length is encoded always by four bytes as in the original version, but the sequence number and CRC32 are omitted, thus decreasing total packet size by 8 bytes.

-

The full, the intermediate and the abridged versions of the protocol have support for quick acknowledgment. In this case, the client sets the highest-order length bit in the query packet, and the server responds with a special 4 bytes as a separate packet. They are the 32 higher-order SHA1 bits of the encrypted portion of the packet with the most significant bit set to make clear that this is not the length of a regular server response packet; if the abridged version is used, bswap is applied to these four bytes.

-

There are no implicit acknowledgments for the TCP transport: all messages must be acknowledged explicitly. Most frequently, acknowledgments are placed in a container with the next query or response if it is transmitted in short order. For example, this is almost always the case for client messages containing RPC queries: the acknowledgment normally arrives with the RPC response.

-

In the event of an error, the server may send a packet whose payload consists of 4 bytes as the error code. For example, Error Code 403 corresponds to situations where the corresponding HTTP error would have been returned by the HTTP protocol.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/passport.html b/data/core.telegram.org/passport.html deleted file mode 100644 index 80b9247f07..0000000000 --- a/data/core.telegram.org/passport.html +++ /dev/null @@ -1,690 +0,0 @@ - - - - - Telegram Passport Manual - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram Passport Manual

- -
- -

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

-

Overview

-

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

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

Check out this example to see Telegram Passport in action.

-
-

To learn more about Telegram Passport from the perspective of a user, please see this blog post and the technical MTProto documentation. -See this page if you're interested in encryption algorithms used on Telegram's side.

-
-

Recent changes

-

August 25, 2018

-

Telegram Passport 1.1 (blog post)

-
    -
  • Added support for requesting several documents of one type. See the new objects PassportScope, PassportScopeElement, PassportScopeElementOneOfSeveral and PassportScopeElementOne.
  • -
  • Added support for middle names.
  • -
  • Added support for requesting certified English translations for documents (see Fields; new field translation also added to the SecureValue object). Note: Please only request translations after you have received a valid document that requires one.
  • -
  • Added support for requesting names in the language of the user's country of residence (if other than English). New fields first_name_native, last_name_native and middle_name_native added to the PersonalDetails object.
  • -
  • Replaced the payload parameter with the new parameter nonce, which serves the same function, to make the purpose more obvious (see Request Parameters and the Credentials object).
  • -
  • Updated the example page to support the new functionality.
  • -
-

Setting Up Telegram Passport

-

To integrate Telegram Passport into your login or verification flow, you need a working Telegram bot (see this page for information on how to get one).

-

To request data from Telegram Passport users, your bot will need to generate a pair of encryption keys.

-

Generating a private key

-

First, use a console to generate a private key:

-
openssl genrsa 2048 > private.key
-

WARNING: Keep your private key SECRET!

-

Generating your public key

-

Then use the console to print the corresponding public key:

-
openssl rsa -in private.key -pubout
-

Use the /setpublickey command with @BotFather to connect this public key with your bot.

-

Privacy Policy

-

Add a link to your Privacy Policy by using the /setprivacypolicy command. Users will see this link when offered to authorize you to access their data.

-

Requesting Information

-

SDK

-

To request information stored in a Telegram Passport, use one of these SDKs:

- -

Request Parameters

-

Use the following parameters to request information with the SDK:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParametersTypeRequired
bot_idIntegerYes
scopePassportScopeYes
public_keyStringYes
nonceStringYes
-

PassportScope

-

This object represents the data to be requested.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
dataArray of PassportScopeElementList of requested elements, each type may be used only once in the entire array of PassportScopeElement objects
vIntegerScope version, must be 1
-

PassportScopeElement

-

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

- -

PassportScopeElementOneOfSeveral

-

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

- - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
one_ofArray of PassportScopeElementOneList of elements one of which must be provided; must contain either several of “passport”, “driver_license”, “identity_card”, “internal_passport” or several of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
selfieBooleanOptional. Use this parameter if you want to request a selfie with the document from this list that the user chooses to upload.
translationBooleanOptional. Use this parameter if you want to request a translation of the document from this list that the user chooses to upload. Note: We suggest to only request translations after you have received a valid document that requires one.
-

PassportScopeElementOne

-

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringElement type. One of "personal_details", "passport", "driver_license", "identity_card", "internal_passport", "address", "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration", "phone_number", "email"
selfieBooleanOptional. Use this parameter if you want to request a selfie with the document as well. Available for "passport", "driver_license", "identity_card" and "internal_passport"
translationBooleanOptional. Use this parameter if you want to request a translation of the document as well. Available for "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration". Note: We suggest to only request translations after you have received a valid document that requires one.
native_namesBooleanOptional. Use this parameter to request the first, last and middle name of the user in the language of the user's country of residence. Available for "personal_details"
-

You can also use the special type "id_document" as an alias for one of "passport", "driver_license", "identity_card" and the special type "address_document" as an alias for one of "utility_bill", "bank_statement", "rental_agreement". -So {"type":"id_document",selfie:true} is equal to {"one_of":["passport","driver_license","identity_card"],selfie:true}.

-

Fields

-

Your bot can request personal details, one or several types of identity document, residential address, one or several types of proof of address document, a phone number, or an email address. You can also request optional selfies with the document and certified English translations of the document. -This is just a list of data types that can be requested, and the encrypted objects that will contain such data.

-
-

Note: We suggest to only request English translations after you have received a valid document that requires one.

-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameKeyTypeDescription
personal_detailsdataPersonalDetailsPersonal Details
passportdataIdDocumentDataPassport
front_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
internal_passportdataIdDocumentDataInternal Passport
front_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
driver_licensedataIdDocumentDataDriver License
front_sidePassportFile
reverse_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
identity_carddataIdDocumentDataIdentity Card
front_sidePassportFile
reverse_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
addressdataResidentialAddressAddress
utility_billfilesArray of PassportFileUtility Bill
translationOptional. Array of PassportFile
bank_statementfilesArray of PassportFileBank Statement
translationOptional. Array of PassportFile
rental_agreementfilesArray of PassportFileRental Agreement
translationOptional. Array of PassportFile
passport_registrationfilesArray of PassportFileRegistration Page in the Internal Passport
translationOptional. Array of PassportFile
temporary_registrationfilesArray of PassportFileTemporary Registration
translationOptional. Array of PassportFile
phone_numberStringPhone number
emailStringEmail
-

PersonalDetails

-

This object represents personal details.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
first_nameStringFirst Name
last_nameStringLast Name
middle_nameStringOptional. Middle Name
birth_dateStringDate of birth in DD.MM.YYYY format
genderStringGender, male or female
country_codeStringCitizenship (ISO 3166-1 alpha-2 country code)
residence_country_codeStringCountry of residence (ISO 3166-1 alpha-2 country code)
first_name_nativeStringFirst Name in the language of the user's country of residence
last_name_nativeStringLast Name in the language of the user's country of residence
middle_name_nativeStringOptional. Middle Name in the language of the user's country of residence
-

ResidentialAddress

-

This object represents a residential address.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
street_line1StringFirst line for the address
street_line2StringOptional. Second line for the address
cityStringCity
stateStringOptional. State
country_codeStringISO 3166-1 alpha-2 country code
post_codeStringAddress post code
-

IdDocumentData

-

This object represents the data of an identity document.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
document_noStringDocument number
expiry_dateStringOptional. Date of expiry, in DD.MM.YYYY format
-

PassportFile

-

This object represents a PassportFile related to a document. The file is up to 10MB in size and in the .jpg format.

-

Receiving information

-

When the user confirms your request by pressing the 'Authorize' button, the Bot API sends an Update with the field passport_data to the bot that contains encrypted Telegram Passport data.

-
-

Note that all base64-encoded fields should be decoded before use.

-
-

Decrypting data

-

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

-
    -
  1. -

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

    -
  2. -
  3. -

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

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

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

    -
  6. -
  7. -

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

    -
  8. -
-
-

Note that all hashes represent as raw binary data, not hexits

-
-

Credentials

-

Credentials is a JSON-serialized object.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
secure_dataSecureDataCredentials for encrypted data
nonceStringBot-specified nonce
-

IMPORTANT: Make sure that the nonce is the same as was passed in the request.

-

SecureData

-

This object represents the credentials required to decrypt encrypted data. All fields are optional and depend on fields that were requested.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
personal_detailsSecureValueOptional. Credentials for encrypted personal details
passportSecureValueOptional. Credentials for encrypted passport
internal_passportSecureValueOptional. Credentials for encrypted internal passport
driver_licenseSecureValueOptional. Credentials for encrypted driver license
identity_cardSecureValueOptional. Credentials for encrypted ID card
addressSecureValueOptional. Credentials for encrypted residential address
utility_billSecureValueOptional. Credentials for encrypted utility bill
bank_statementSecureValueOptional. Credentials for encrypted bank statement
rental_agreementSecureValueOptional. Credentials for encrypted rental agreement
passport_registrationSecureValueOptional. Credentials for encrypted registration from internal passport
temporary_registrationSecureValueOptional. Credentials for encrypted temporary registration
-

SecureValue

-

This object represents the credentials required to decrypt encrypted values. All fields are optional and depend on the type of fields that were requested.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
dataDataCredentialsOptional. Credentials for encrypted Telegram Passport data. Available for "personal_details", "passport", "driver_license", "identity_card", "internal_passport" and "address" types.
front_sideFileCredentialsOptional. Credentials for an encrypted document's front side. Available for "passport", "driver_license", "identity_card" and "internal_passport".
reverse_sideFileCredentialsOptional. Credentials for an encrypted document's reverse side. Available for "driver_license" and "identity_card".
selfieFileCredentialsOptional. Credentials for an encrypted selfie of the user with a document. Available for "passport", "driver_license", "identity_card" and "internal_passport".
translationArray of FileCredentialsOptional. Credentials for an encrypted translation of the document. Available for "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration".
filesArray of FileCredentialsOptional. Credentials for encrypted files. Available for "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration" types.
-

DataCredentials

-

These credentials can be used to decrypt encrypted data from the data field in EncryptedPassportElement.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
data_hashStringChecksum of encrypted data
secretStringSecret of encrypted data
-
    -
  1. -

    To decrypt data, use the corresponding secret and data_hash from DataCredentials as described below:

    -
     data_secret_hash = SHA512( data_secret + data_hash )
    - data_key = slice( data_secret_hash, 0, 32 )
    - data_iv = slice( data_secret_hash, 32, 16 )
    -
  2. -
  3. -

    Use AES256-CBC with this data_key and data_iv to decrypt the data (the data field in EncryptedPassportElement). IMPORTANT: At this step, make sure that data_hash from the credentials is equal to SHA256( data ).

    -
  4. -
  5. -

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

    -
  6. -
  7. -

    The data is a JSON-serialized object of one of the following types: PersonalDetails, IdDocumentData, ResidentialAddress, depending on type.

    -
  8. -
-

FileCredentials

-

These credentials can be used to decrypt encrypted files from the front_side, reverse_side, selfie, files and translation fields in EncryptedPassportElement.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_hashStringChecksum of encrypted file
secretStringSecret of encrypted file
-
    -
  1. -

    To decrypt the file, use the corresponding secret and file_hash from FileCredentials as described below:

    -
     file_secret_hash = SHA512( file_secret + file_hash )
    - file_key = slice( file_secret_hash, 0, 32 )
    - file_iv = slice( file_secret_hash, 32, 16 )
    -
  2. -
  3. -

    Download the encrypted file using the getFile method.

    -
  4. -
  5. -

    Use AES256-CBC with this file_key and file_iv to decrypt the content of the file. IMPORTANT: At this step, make sure that file_hash from the credentials is equal to SHA256( file_content ).

    -
  6. -
  7. -

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

    -
  8. -
-

Fixing errors

-

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

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/passport/sdk-android.html b/data/core.telegram.org/passport/sdk-android.html deleted file mode 100644 index a44201d52b..0000000000 --- a/data/core.telegram.org/passport/sdk-android.html +++ /dev/null @@ -1,180 +0,0 @@ - - - - - Android SDK - - - - - - - - - - - - - -
- -
-
-
- -

Android SDK

- -
- -

The Android SDK helps you easily integrate Telegram Passport requests into your Android-based apps. Check out our GitHub repository to see samples using this SDK.

-

Installation

-

Installing from Maven

-

Telegram Passport SDK is available from the Maven repository. -Add this line to the dependencies section in your build.gradle:

-
compile 'org.telegram:passport:1.1'
-

and sync your project.

-

Adding as a module

-

Download the library, unzip it and copy the library project to the root of your project directory (the one with settings.gradle and gradle.properties). Then, make the following changes to your Gradle scripts.

-

In settings.gradle, add ':telegrampassport' to includes:

-
include ':app', ':telegrampassport'
-

In the build.gradle file for your app, add this line to the dependencies section:

-
compile ':telegrampassport'
-

and sync your project.

-

Usage

-

Adding the button

-

The SDK provides the "Log in with Telegram" button which we recommend using for a consistent user experience across different apps. You can either add it from your Java code:

-
TelegramLoginButton telegramButton;
-// ...
-telegramButton=new TelegramLoginButton(this);
-// Optionally you can change the roundness of the button corners
-// to better fit your design.
-telegramButton.setCornerRoundness(1f);
-viewGroupOfSomeSort.addView(telegramButton, ViewGroup.LayoutParams.WRAP_CONTENT, ViewGroup.LayoutParams.WRAP_CONTENT);
-

Or from XML:

-
 <org.telegram.passport.TelegramLoginButton
-             android:layout_width="wrap_content"
-             android:layout_height="wrap_content"
-             app:cornerRoundness="0.5"/>
-

Requesting authorization

-

The button doesn't do anything by itself; you need to set an OnClickListener on it to start the authorization flow (replace the comments with actual parameters):

-
private static final int TG_PASSPORT_RESULT=352; // this can be any integer less than 0xFFFF
-// ...
-telegramButton.setOnClickListener(new View.OnClickListener(){
-@Override
-public void onClick(View view){
-    TelegramPassport.AuthRequest req=new TelegramPassport.AuthRequest();
-    req.botID=/* your bot ID here */;
-    req.publicKey=/* your bot public key here */;
-    req.nonce=/* a unique nonce to pass to the bot server */;
-    // Request either a passport or an ID card with selfie, a driver license, personal details with
-    // name as it appears in the documents, address with any address document, and a phone number.
-    // You could also pass a raw JSON object here if that's what works better for you
-    // (for example, if you already get it from your server in the correct format).
-    req.scope=new PassportScope(
-        new PassportScopeElementOneOfSeveral(PassportScope.PASSPORT, PassportScope.IDENTITY_CARD).withSelfie(),
-        new PassportScopeElementOne(PassportScope.PERSONAL_DETAILS).withNativeNames(),
-        PassportScope.DRIVER_LICENSE,
-        PassportScope.ADDRESS,
-        PassportScope.ADDRESS_DOCUMENT,
-        PassportScope.PHONE_NUMBER
-    );
-    TelegramPassport.request(MyActivity.this, req, TG_PASSPORT_RESULT);
-}});
-

If you need more control over the process, the TelegramPassport class contains several more methods:

-
    -
  • getAuthIntent(AuthParams) returns an Intent for you to use in startActivityForResult if you need to do that in some special way. Be sure to check that an app is present that can handle this intent before starting it by using PackageManager or intent.resolveActivity.
  • -
  • showAppInstallAlert(Activity) shows an alert that the user needs to install Telegram in order to continue. This is intended to be used together with the previous method for the cases when the app isn't installed.
  • -
-

Handling the result

-

The result is delivered via the onActivityResult method in your activity with the request code you passed to TelegramPassport.request. Currently, the only meaningful parameter is resultCode, which is RESULT_OK if the authorization was successful and RESULT_CANCELED otherwise.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/tdlib.html b/data/core.telegram.org/tdlib.html deleted file mode 100644 index dee8b1f4ba..0000000000 --- a/data/core.telegram.org/tdlib.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - Telegram Database Library - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram Database Library

- -
- -
- -

TDLib (Telegram Database Library) is a cross-platform, fully functional Telegram client. We designed it to help third-party developers create their own custom apps using the Telegram platform.

-
-

Read about TDLib on the Telegram blog »

-
-

TDLib Advantages

-
    -
  • Cross-platform. TDLib can be used on Android, iOS, Windows, macOS, Linux, WebAssembly, FreeBSD, Windows Phone, watchOS, tvOS, Tizen, Cygwin. It should also work on other *nix systems with or without minimal effort.
  • -
  • Multilanguage. TDLib can be easily used with any programming language that is able to execute C functions. Additionally it already has native bindings to Java (using JNI) and C# (using C++/CLI).
  • -
  • Easy to use. TDLib takes care of all network implementation details, encryption and local data storage.
  • -
  • High-performance. In the Telegram Bot API, each TDLib instance handles more than 24,000 active bots simultaneously.
  • -
  • Well-documented. All TDLib API methods and public interfaces are fully documented.
  • -
  • Consistent. TDLib guarantees that all updates will be delivered in the right order.
  • -
  • Reliable. TDLib remains stable on slow and unreliable Internet connections.
  • -
  • Secure: All local data is encrypted using a user-provided encryption key.
  • -
  • Fully-asynchronous. Requests to TDLib don't block each other or anything else, responses will be sent when they are available.
  • -
-
-

Getting started with TDLib »

-
-

Resources

-

TDLib is fully open source, all code is available on GitHub.

-

See also:

- -
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/CdnPublicKey.html b/data/core.telegram.org/type/CdnPublicKey.html deleted file mode 100644 index b1b845c5b8..0000000000 --- a/data/core.telegram.org/type/CdnPublicKey.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - CdnPublicKey - - - - - - - - - - - - - -
- -
-
-
- -

CdnPublicKey

- -

Public key to use only during handshakes to CDN DCs.

-

-
cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
cdnPublicKeyPublic key to use only during handshakes to CDN DCs.
-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChatInvite.html b/data/core.telegram.org/type/ChatInvite.html deleted file mode 100644 index 914a41c105..0000000000 --- a/data/core.telegram.org/type/ChatInvite.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - ChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

ChatInvite

- -

Chat invite

-

-
chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
-chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
-chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
-
----functions---
-
-messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
chatInviteAlreadyThe user has already joined this chat
chatInviteChat invite info
chatInvitePeekA chat invitation that also allows peeking into the group to read messages without joining it.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.checkChatInviteCheck the validity of a chat invite link and get basic info about it
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DcOption.html b/data/core.telegram.org/type/DcOption.html deleted file mode 100644 index 83c46fc0de..0000000000 --- a/data/core.telegram.org/type/DcOption.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - DcOption - - - - - - - - - - - - - -
- -
-
-
- -

DcOption

- -

Information for connection to data centre.

-

-
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
dcOptionData centre
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DecryptedMessage.html b/data/core.telegram.org/type/DecryptedMessage.html deleted file mode 100644 index 18e5ee15d7..0000000000 --- a/data/core.telegram.org/type/DecryptedMessage.html +++ /dev/null @@ -1,140 +0,0 @@ - - - - - DecryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

DecryptedMessage

- -

Object describes the contents of an encrypted message.

-

-
===8===
-decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
-decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
-
-===17===
-decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
-decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;
-
-===45===
-decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
-
-===73===
-decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DecryptedMessageMedia.html b/data/core.telegram.org/type/DecryptedMessageMedia.html deleted file mode 100644 index bf28500b9d..0000000000 --- a/data/core.telegram.org/type/DecryptedMessageMedia.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - DecryptedMessageMedia - - - - - - - - - - - - - -
- -
-
-
- -

DecryptedMessageMedia

- -

Object describes media contents of an encrypted message.

-

-
===8===
-decryptedMessageMediaEmpty#89f5c4a = DecryptedMessageMedia;
-decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;
-decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;
-decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===17===
-decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===23===
-decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;
-
-===45===
-decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
-decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
-decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;
-decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;
-decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputEncryptedFile.html b/data/core.telegram.org/type/InputEncryptedFile.html deleted file mode 100644 index f9ee3d5645..0000000000 --- a/data/core.telegram.org/type/InputEncryptedFile.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputEncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

InputEncryptedFile

- -

Object sets encrypted file for attachment

-

-
inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;
-inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
-inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;
-inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputEncryptedFileEmptyEmpty constructor.
inputEncryptedFileUploadedSets new encrypted file saved by parts using upload.saveFilePart method.
inputEncryptedFileSets forwarded encrypted file for attachment.
inputEncryptedFileBigUploadedAssigns a new big encrypted file (over 10Mb in size), saved in parts using the method upload.saveBigFilePart.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputPhoneCall.html b/data/core.telegram.org/type/InputPhoneCall.html deleted file mode 100644 index fcbe17ef2b..0000000000 --- a/data/core.telegram.org/type/InputPhoneCall.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputPhoneCall - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/type/InputWallPaper.html b/data/core.telegram.org/type/InputWallPaper.html deleted file mode 100644 index 4f6f36b6af..0000000000 --- a/data/core.telegram.org/type/InputWallPaper.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - InputWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

InputWallPaper

- -

Wallpaper

-

-
inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;
-inputWallPaperSlug#72091c80 slug:string = InputWallPaper;
-inputWallPaperNoFile#8427bbac = InputWallPaper;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputWallPaperWallpaper
inputWallPaperSlugWallpaper by slug (a unique ID)
inputWallPaperNoFileWallpaper with no file
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/LabeledPrice.html b/data/core.telegram.org/type/LabeledPrice.html deleted file mode 100644 index ad2cfd78f5..0000000000 --- a/data/core.telegram.org/type/LabeledPrice.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - LabeledPrice - - - - - - - - - - - - - -
- -
-
-
- -

LabeledPrice

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/LangPackDifference.html b/data/core.telegram.org/type/LangPackDifference.html deleted file mode 100644 index a4d700c8a5..0000000000 --- a/data/core.telegram.org/type/LangPackDifference.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - LangPackDifference - - - - - - - - - - - - - -
- -
-
-
- -

LangPackDifference

- -

Language pack changes

-

-
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
-
----functions---
-
-langpack.getLangPack#f2f2330a lang_pack:string lang_code:string = LangPackDifference;
-langpack.getDifference#cd984aa5 lang_pack:string lang_code:string from_version:int = LangPackDifference;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
langPackDifferenceChanges to the app's localization pack
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
langpack.getLangPackGet localization pack strings
langpack.getDifferenceGet new strings in languagepack
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageEntity.html b/data/core.telegram.org/type/MessageEntity.html deleted file mode 100644 index 0e632188ac..0000000000 --- a/data/core.telegram.org/type/MessageEntity.html +++ /dev/null @@ -1,233 +0,0 @@ - - - - - MessageEntity - - - - - - - - - - - - - -
- -
-
-
- -

MessageEntity

- -

Message entities, representing styled text in a message

-

-
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
-messageEntityMention#fa04579d offset:int length:int = MessageEntity;
-messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
-messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
-messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
-messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
-messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
-messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
-messageEntityCode#28a20571 offset:int length:int = MessageEntity;
-messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
-messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
-messageEntityMentionName#352dca58 offset:int length:int user_id:int = MessageEntity;
-inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
-messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;
-messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;
-messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;
-messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;
-messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;
-messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messageEntityUnknownUnknown message entity
messageEntityMentionMessage entity mentioning the current user
messageEntityHashtag#hashtag message entity
messageEntityBotCommandMessage entity representing a bot /command
messageEntityUrlMessage entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.
messageEntityEmailMessage entity representing an email@example.com.
messageEntityBoldMessage entity representing bold text.
messageEntityItalicMessage entity representing italic text.
messageEntityCodeMessage entity representing a codeblock.
messageEntityPreMessage entity representing a preformatted codeblock, allowing the user to specify a programming language for the codeblock.
messageEntityTextUrlMessage entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.
messageEntityMentionNameMessage entity representing a user mention: for creating a mention use inputMessageEntityMentionName.
inputMessageEntityMentionNameMessage entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.
messageEntityPhoneMessage entity representing a phone number.
messageEntityCashtagMessage entity representing a $cashtag.
messageEntityUnderlineMessage entity representing underlined text.
messageEntityStrikeMessage entity representing strikethrough text.
messageEntityBlockquoteMessage entity representing a block quote.
messageEntityBankCardIndicates a credit card number
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageInteractionCounters.html b/data/core.telegram.org/type/MessageInteractionCounters.html deleted file mode 100644 index 61b7b5537c..0000000000 --- a/data/core.telegram.org/type/MessageInteractionCounters.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MessageInteractionCounters - - - - - - - - - - - - - -
- -
-
-
- -

MessageInteractionCounters

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageMedia.html b/data/core.telegram.org/type/MessageMedia.html deleted file mode 100644 index 5e7e743adc..0000000000 --- a/data/core.telegram.org/type/MessageMedia.html +++ /dev/null @@ -1,227 +0,0 @@ - - - - - MessageMedia - - - - - - - - - - - - - -
- -
-
-
- -

MessageMedia

- -

Media

-

-
messageMediaEmpty#3ded6320 = MessageMedia;
-messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
-messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
-messageMediaContact#cbf24940 phone_number:string first_name:string last_name:string vcard:string user_id:int = MessageMedia;
-messageMediaUnsupported#9f84f49e = MessageMedia;
-messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
-messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
-messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
-messageMediaGame#fdb19008 game:Game = MessageMedia;
-messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
-messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
-messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
-messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
-
----functions---
-
-messages.getWebPagePreview#8b68b0cc flags:# message:string entities:flags.3?Vector<MessageEntity> = MessageMedia;
-messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messageMediaEmptyEmpty constructor.
messageMediaPhotoAttached photo.
messageMediaGeoAttached map.
messageMediaContactAttached contact.
messageMediaUnsupportedCurrent version of the client does not support this media type.
messageMediaDocumentDocument (video, audio, voice, sticker, any media type except photo)
messageMediaWebPagePreview of webpage
messageMediaVenueVenue
messageMediaGameTelegram game
messageMediaInvoiceInvoice
messageMediaGeoLiveIndicates a live geolocation
messageMediaPollPoll
messageMediaDiceDice
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getWebPagePreviewGet preview of webpage
messages.uploadMediaUpload a file and associate it to a chat (without actually sending it to the chat)
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageReactionsList.html b/data/core.telegram.org/type/MessageReactionsList.html deleted file mode 100644 index 9b7f6be3f2..0000000000 --- a/data/core.telegram.org/type/MessageReactionsList.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - MessageReactionsList - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/type/Page.html b/data/core.telegram.org/type/Page.html deleted file mode 100644 index 3a80037009..0000000000 --- a/data/core.telegram.org/type/Page.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Page - - - - - - - - - - - - - -
- -
-
-
- -

Page

- -

Instant view page

-

-
page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pageInstant view page
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Peer.html b/data/core.telegram.org/type/Peer.html deleted file mode 100644 index 73cd205a42..0000000000 --- a/data/core.telegram.org/type/Peer.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - Peer - - - - - - - - - - - - - -
- -
-
-
- -

Peer

- -

Chat partner or group.

-

-
peerUser#9db1bc6d user_id:int = Peer;
-peerChat#bad0e5bb chat_id:int = Peer;
-peerChannel#bddde532 channel_id:int = Peer;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
peerUserChat partner
peerChatGroup.
peerChannelChannel/supergroup
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PhoneCall.html b/data/core.telegram.org/type/PhoneCall.html deleted file mode 100644 index 22dff2a22f..0000000000 --- a/data/core.telegram.org/type/PhoneCall.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - PhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

PhoneCall

- -

Phone call

-

-
phoneCallEmpty#5366c915 id:long = PhoneCall;
-phoneCallWaiting#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;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
phoneCallEmptyEmpty constructor
phoneCallWaitingIncoming phone call
phoneCallRequestedRequested phone call
phoneCallAcceptedAn accepted phone call
phoneCallPhone call
phoneCallDiscardedIndicates a discarded phone call
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PhotoSize.html b/data/core.telegram.org/type/PhotoSize.html deleted file mode 100644 index 8515b49db0..0000000000 --- a/data/core.telegram.org/type/PhotoSize.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - PhotoSize - - - - - - - - - - - - - -
- -
-
-
- -

PhotoSize

- -

Location of a certain size of a picture

-

-
photoSizeEmpty#e17e23c type:string = PhotoSize;
-photoSize#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;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
photoSizeEmptyEmpty constructor. Image with this thumbnail is unavailable.
photoSizeImage description.
photoCachedSizeDescription of an image and its content.
photoStrippedSizeJust the image's content
photoSizeProgressiveProgressively encoded photosize
photoPathSizeMessages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SendMessageAction.html b/data/core.telegram.org/type/SendMessageAction.html deleted file mode 100644 index d7cf006d0a..0000000000 --- a/data/core.telegram.org/type/SendMessageAction.html +++ /dev/null @@ -1,203 +0,0 @@ - - - - - SendMessageAction - - - - - - - - - - - - - -
- -
-
-
- -

SendMessageAction

- -

User actions. Use this to provide users with detailed info about their chat partners' actions: typing or sending attachments of all kinds.

-

-
sendMessageTypingAction#16bf744e = SendMessageAction;
-sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
-sendMessageRecordVideoAction#a187d66f = SendMessageAction;
-sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;
-sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
-sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;
-sendMessageUploadPhotoAction#d1d34a26 progress:int = SendMessageAction;
-sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;
-sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
-sendMessageChooseContactAction#628cbc6f = SendMessageAction;
-sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;
-sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
-sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
sendMessageTypingActionUser is typing.
sendMessageCancelActionInvalidate all previous action updates. E.g. when user deletes entered text or aborts a video upload.
sendMessageRecordVideoActionUser is recording a video.
sendMessageUploadVideoActionUser is uploading a video.
sendMessageRecordAudioActionUser is recording a voice message.
sendMessageUploadAudioActionUser is uploading a voice message.
sendMessageUploadPhotoActionUser is uploading a photo.
sendMessageUploadDocumentActionUser is uploading a file.
sendMessageGeoLocationActionUser is selecting a location to share.
sendMessageChooseContactActionUser is selecting a contact to share.
sendMessageGamePlayActionUser is playing a game
sendMessageRecordRoundActionUser is recording a round video to share
sendMessageUploadRoundActionUser is uploading a round video
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.Password b/data/core.telegram.org/type/account.Password deleted file mode 100644 index e7fd4354e1..0000000000 --- a/data/core.telegram.org/type/account.Password +++ /dev/null @@ -1,162 +0,0 @@ - - - - - account.Password - - - - - - - - - - - - - -
- -
-
-
- -

account.Password

- -

Configuration for two-factor authorization

-

-
account.password#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;
-
----functions---
-
-account.getPassword#548a30f5 = account.Password;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.passwordConfiguration for two-factor authorization
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getPasswordObtain configuration for two-factor authorization with password
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.TmpPassword b/data/core.telegram.org/type/account.TmpPassword deleted file mode 100644 index e287a186d6..0000000000 --- a/data/core.telegram.org/type/account.TmpPassword +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.TmpPassword - - - - - - - - - - - - - -
- -
-
-
- -

Account.TmpPassword

- -

Temporary password

-

-
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
-
----functions---
-
-account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.tmpPasswordTemporary payment password
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getTmpPasswordGet temporary payment password
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/help.PromoData b/data/core.telegram.org/type/help.PromoData deleted file mode 100644 index 22e708e247..0000000000 --- a/data/core.telegram.org/type/help.PromoData +++ /dev/null @@ -1,167 +0,0 @@ - - - - - help.PromoData - - - - - - - - - - - - - -
- -
-
-
- -

help.PromoData

- -

Info about pinned MTProxy or Public Service Announcement peers.

-

-
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
-help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
-
----functions---
-
-help.getPromoData#c0977421 = help.PromoData;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.promoDataEmptyNo PSA/MTProxy info is available
help.promoDataMTProxy/Public Service Announcement information
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getPromoDataGet MTProxy/Public Service Announcement information
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/int.html b/data/core.telegram.org/type/int.html deleted file mode 100644 index 5a6f6bdc91..0000000000 --- a/data/core.telegram.org/type/int.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - - int - - - - - - - - - - - - - -
- -
-
-
- -

int

- -

A basic bare type, the values of which correspond to single-element sequences, i.e. numbers from -2^31 to 2^31-1 which in this case represent themselves.

-

More on basic types »

-

Related pages

-

Binary Data Serialization

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.ChatFull b/data/core.telegram.org/type/messages.ChatFull deleted file mode 100644 index e9ed919416..0000000000 --- a/data/core.telegram.org/type/messages.ChatFull +++ /dev/null @@ -1,168 +0,0 @@ - - - - - messages.ChatFull - - - - - - - - - - - - - -
- -
-
-
- -

messages.ChatFull

- -

Object contains extended info on chat with auxiliary data.

-

-
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
-
----functions---
-
-messages.getFullChat#3b831c66 chat_id:int = messages.ChatFull;
-
-channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.chatFullExtended info on chat and auxiliary data.
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getFullChatReturns full chat info according to its ID.
channels.getFullChannelGet full info about a channel
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.FavedStickers b/data/core.telegram.org/type/messages.FavedStickers deleted file mode 100644 index a0ccb34ea5..0000000000 --- a/data/core.telegram.org/type/messages.FavedStickers +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.FavedStickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.FavedStickers

- -

Favorited stickers

-

-
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
-messages.favedStickers#f37f2f16 hash:int packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
-
----functions---
-
-messages.getFavedStickers#21ce0b0e hash:int = messages.FavedStickers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.favedStickersNotModifiedNo new favorited stickers were found
messages.favedStickersFavorited stickers
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getFavedStickersGet faved stickers
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.FoundStickerSets b/data/core.telegram.org/type/messages.FoundStickerSets deleted file mode 100644 index 2bd1e3e508..0000000000 --- a/data/core.telegram.org/type/messages.FoundStickerSets +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.FoundStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

Messages.FoundStickerSets

- -

Found stickersets

-

-
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
-messages.foundStickerSets#5108d648 hash:int sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
-
----functions---
-
-messages.searchStickerSets#c2b7d08b flags:# exclude_featured:flags.0?true q:string hash:int = messages.FoundStickerSets;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.foundStickerSetsNotModifiedNo further results were found
messages.foundStickerSetsFound stickersets
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.searchStickerSetsSearch for stickersets
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.Messages b/data/core.telegram.org/type/messages.Messages deleted file mode 100644 index 82ac2ef639..0000000000 --- a/data/core.telegram.org/type/messages.Messages +++ /dev/null @@ -1,229 +0,0 @@ - - - - - messages.Messages - - - - - - - - - - - - - -
- -
-
-
- -

messages.Messages

- -

Object contains infor on list of messages with auxiliary data.

-

-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
-
----functions---
-
-messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;
-messages.getHistory#dcbb8260 peer:InputPeer offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:int = messages.Messages;
-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;
-messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
-messages.getRecentLocations#bbc45b09 peer:InputPeer limit:int hash:int = messages.Messages;
-messages.getScheduledHistory#e2c2685b peer:InputPeer hash:int = messages.Messages;
-messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;
-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;
-
-channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;
-
-stats.getMessagePublicForwards#5630281b channel:InputChannel msg_id:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.messagesFull list of messages with auxilary data.
messages.messagesSliceIncomplete list of messages and auxiliary data.
messages.channelMessagesChannel messages
messages.messagesNotModifiedNo new messages matching the query were found
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.getMessagesReturns the list of messages by their IDs.
messages.getHistoryGets back the conversation history with one interlocutor / within a chat
messages.searchGets back found messages
channels.getMessagesGet channel/supergroup messages
messages.searchGlobalSearch for messages and peers globally
messages.getUnreadMentionsGet unread messages where we were mentioned
messages.getRecentLocationsGet live location history of a certain user
messages.getScheduledHistoryGet scheduled messages
messages.getScheduledMessagesGet scheduled messages
messages.getRepliesGet messages in a reply thread
stats.getMessagePublicForwardsObtains a list of messages, indicating to which other public channels was a channel message forwarded.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.PeerDialogs b/data/core.telegram.org/type/messages.PeerDialogs deleted file mode 100644 index fabdf9cb3a..0000000000 --- a/data/core.telegram.org/type/messages.PeerDialogs +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.PeerDialogs - - - - - - - - - - - - - -
- -
-
-
- -

Messages.PeerDialogs

- -

List of dialogs

-

-
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
-
----functions---
-
-messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;
-messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.peerDialogsDialog info of multiple peers
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getPeerDialogsGet dialog info of specified peers
messages.getPinnedDialogsGet pinned dialogs
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.VotesList b/data/core.telegram.org/type/messages.VotesList deleted file mode 100644 index 8586a63bdc..0000000000 --- a/data/core.telegram.org/type/messages.VotesList +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.VotesList - - - - - - - - - - - - - -
- -
-
-
- -

messages.VotesList

- -

How users voted in a poll

-

-
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;
-
----functions---
-
-messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.votesListHow users voted in a poll
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getPollVotesGet poll results for non-anonymous polls
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/payments.SavedInfo b/data/core.telegram.org/type/payments.SavedInfo deleted file mode 100644 index 5fc6332ace..0000000000 --- a/data/core.telegram.org/type/payments.SavedInfo +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Payments.SavedInfo - - - - - - - - - - - - - -
- -
-
-
- -

Payments.SavedInfo

- -

Saved payment info

-

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

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
payments.savedInfoSaved server-side order information
-

Methods

- - - - - - - - - - - - - -
MethodDescription
payments.getSavedInfoGet saved payment information
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/string.html b/data/core.telegram.org/type/string.html deleted file mode 100644 index 472761b35a..0000000000 --- a/data/core.telegram.org/type/string.html +++ /dev/null @@ -1,126 +0,0 @@ - - - - - string - - - - - - - - - - - - - -
- -
-
-
- -

string

- -

A basic bare type. Values of type string look differently depending on the length L of the string being serialized:

-
    -
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit little-endian integers.
  • -
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L in little-endian order, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • -
-

All strings passed to the API must be encoded in UTF-8. When arbitrary byte sequences have to be serialized, bytes alias is to be used.

-

Further details on basic types»

-

Related pages

-

bytes

-

Basic bare type. It is an alias of the string type, with the difference that the value may contain arbitrary byte sequences, including invalid UTF-8 sequences.

-

When computing crc32 for a constructor or method it is necessary to replace all byte types with string types.

-

Binary Data Serialization

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/upload.CdnFile b/data/core.telegram.org/type/upload.CdnFile deleted file mode 100644 index 28223e59fb..0000000000 --- a/data/core.telegram.org/type/upload.CdnFile +++ /dev/null @@ -1,167 +0,0 @@ - - - - - upload.CdnFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.CdnFile

- -

Represents the download status of a CDN file

-

-
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
-upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
-
----functions---
-
-upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
upload.cdnFileReuploadNeededThe file was cleared from the temporary RAM cache of the CDN and has to be reuploaded.
upload.cdnFileRepresent a chunk of a CDN file.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
upload.getCdnFileDownload a CDN file.
- -
- -
-
- -
- - - - - - diff --git a/data/telegram.org/blog/edit.html b/data/telegram.org/blog/edit.html deleted file mode 100644 index f8f936f25f..0000000000 --- a/data/telegram.org/blog/edit.html +++ /dev/null @@ -1,245 +0,0 @@ - - - - - Edit Messages, New Mentions and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Edit Messages, New Mentions and More

- -
- -
- -

Farewell to typos! Starting today, you can edit the text of your messages after sending them. This works across all Telegram chats, including groups and one-on-one conversations.

-
- -

Edit messages

-
- -

Simply tap and hold on a message, then press ‘Edit’. If you're on desktop, press the up arrow button to edit your last message. The messages will display a small ‘edited’ label so that it's easy to tell which were altered.

-

New Mentions

-

Mentioning other people in groups is handy since it sends them a notification about your message even if they muted the group. Starting today, you can mention any members in a group – even if they don't have a username. Just type the @ symbol and select whoever you would like to address. Easy!

-
- -

Mention group members

-
- -

People List

-

Speaking of addressing people, you can now get to your recent chats much faster using the new People list in Search.

-
- -

Recent chats

-
- - -

Bot Attachments

-

We've also made it easier for you to access your favorite inline bots. Simply scroll down the attachment menu – and there they are. The more you use them, the higher they will climb.

-
- -

Bots in attachment menu

-
- -

Naturally, you will only see inline bots in the attachment menu if you used them at least once. Try @youtube, @gif or @imdb if you don't know where to start. Check out this post for more info on how to use inline bots.

-

Interface Improvements

-

We‘ve added quick sharing buttons to forwarded messages from bots, channels, and public groups. Notifications about messages with stickers will now show the relevant emoji so that you’ll know the general idea at first glance.

-
- -

Scroll to bottom

-
- -

Last but not least, if you're on iOS, your app now remembers the scroll position in chats when switching to a different chat and back. And scrolling up in a chat summons a new button that will send you back to the bottom in one tap. This button also displays a handy unread message counter if new ones are waiting for you there.

-

- -

And that's it for today. Stay tuned for more updates coming soon!

-

- -

May 15, 2016
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/inline-bots.html b/data/telegram.org/blog/inline-bots.html deleted file mode 100644 index 81e89cbaaa..0000000000 --- a/data/telegram.org/blog/inline-bots.html +++ /dev/null @@ -1,234 +0,0 @@ - - - - - Introducing Inline Bots - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Introducing Inline Bots

- -
- -
- -

Bots became an integral part of Telegram for many users, but communication with them wasn't always easy. You had to send them messages in separate chats or add them to your groups. Today we are introducing a quicker way to contact bots.

-

With the new inline mode, bots become omnipresent and can be used as a tool in any of your chats, groups or channels – it doesn't matter, whether the bot is a member or not. Inline bots can help you with dozens of different tasks, like quickly sending relevant GIFs, pictures from the Web, YouTube videos, Wikipedia articles, etc.

-
-
- -
-
- -

How does it work?

-

We've created several sample bots for you to try out: @gif, @vid, @pic, @bing, @wiki, @imdb and @bold. To see them in action, simply type one of their @usernames in the message field in any chat, then type some keywords. The bot will offer you relevant content.

-
- - -
-
- - -

Tap on an item to instantly send it to the chat. This way you can share stuff from bots without any hassle. Inline bots don't see any messages in your chats – they only receive what you type after their username in the input field.

-
- - -
-
- -

Tap on ‘via @username’ to send a new request to the bot. Recently used inline bots will also show up in the suggestion box when you type @ in the input field in any chat.

-

A new dimension for bots

-

Like pretty much everything else at Telegram, inline bots are part of an open platform, available for free to every developer in the world starting today. Hundreds of new inline bots are sure to arrive once developers start supporting the new mode.

-

If you are a developer, take a look at our Introduction to Inline Bots. Also, feel free to subscribe to our official @BotNews channel to stay up to date on platform news.

-

- -

The Telegram Team,
January 4, 2016

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/polls-2-0-vmq.html b/data/telegram.org/blog/polls-2-0-vmq.html deleted file mode 100644 index 67c393fed7..0000000000 --- a/data/telegram.org/blog/polls-2-0-vmq.html +++ /dev/null @@ -1,271 +0,0 @@ - - - - - Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode

- -
- -
- -
- Introducing Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode -
- -

Since we first added polls for groups and channels, they've been used for everything from deciding where to have lunch to organizing leaderless protests. Today we're expanding the range of possibilities with three new kinds of Telegram polls.

-
- -
- -

Visible Votes

-

Previously, all polls on Telegram were anonymous. With this update, you can create polls that allow everyone in the group to see who voted for what. Now you will know exactly which friends you disagree with on the matter of pineapple and pizza.

-
- A poll that shows who voted for which option -
- -

Naturally, you can still create anonymous polls to make sure nobody finds out it was you who voted for broccoli instead of cookies.

-

Multiple Answers

-

One of the best ways to settle the score is with polls that allow people to select multiple answers. Scheduling events, or choosing a playlist of songs for a party – sometimes you need more than one choice.

-
- A poll that allows people to select multiple answers -
- -

Our aunt who has a knack for statistics and exploring bizarre correlations kept asking for this feature – and we just couldn't say no. (33% of developers who didn't refuse this request were also found to be addicted to cheese.)

-

Quiz Mode

-

For the game show guru and “Who Wants To Be A Millionaire” contestant in all of us, polls now have Quiz Mode. Such polls have one correct answer and can power anything from trivia games to public service exams.

-
- Quiz mode -
- -

As if guessing right wasn't sweet enough, correct answers will trigger a shower of confetti.

-

Creating Polls

-

Polls can be created in groups or channels (they feel lonely in one-on-one chats). Simply choose the “Poll” option in the attachment menu. Type in your question, add answer options, choose the settings that fit your purpose best – and you're ready to go:

-
- -
- -

Bot API and Quiz Bot

-

All the new poll types are supported in today's update to our Bot API, so bot developers can build on this new functionality.

-

As an example, we've created a Quiz Bot that lets you create multi-question quizzes and share them with others. It also lets you add text or media before questions to help create exam-style prompts with graphs and tables – or better yet, your own Know Your Meme tests.

-

Once your quiz is ready, you can share it to a group or channel – or invite users to answer questions privately, in a chat with the bot. To see how this works, try our demo quiz: Who is Who in the 'Great Minds' sticker pack.

-
- Demo Quiz -
- -

The bot will keep tabs on how many questions users got right and how much time it took them to complete the quiz. It also keeps a global leaderboard for each quiz you create.

-

Message Corners

-

In addition to the new polls, our apps just got a new visual setting. If you find your Telegram messages too hip to be square (or round, depending on your platform), you can tweak the appearance of message bubbles in Settings:

-
- -
- -

Download Progress Counters on Android

-

Just like on iOS, Android users can now see exact progress counters when downloading or uploading files – if they're in the mood to count bits and bytes.

-
- Download progress counters on Android -
- -

And that's it for today. Here's to a good new year full of updates. Stay tuned!

-

- -

January 23, 2020
The Telegram Team

-
- -
- -
- -
-
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/faq.html b/data/telegram.org/faq.html deleted file mode 100644 index ed7e1b81a4..0000000000 --- a/data/telegram.org/faq.html +++ /dev/null @@ -1,705 +0,0 @@ - - - - - Telegram FAQ - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
-
-

Telegram FAQ

- -
-

This FAQ provides answers to basic questions about Telegram.
Check out our Advanced FAQ for more technical information.

-
-

-

General

- -

Telegram Basics

- -

Groups and Channels

- -

Usernames and t.me

- -

Security

- -

Secret Chats

- -

Your Account

- -

Bots

- -

Deeper Questions

- -

Troubleshooting

- -

Contact Telegram Support
Follow Us on Twitter
Facebook
Advanced FAQ

-

-
-

General Questions

-

Q: What is Telegram? What do I do here?

-

Telegram is a messaging app with a focus on speed and security, it’s super-fast, simple and free. You can use Telegram on all your devices at the same time — your messages sync seamlessly across any number of your phones, tablets or computers. Telegram has over 500 million monthly active users and is one of the 10 most downloaded apps in the world.

-

With Telegram, you can send messages, photos, videos and files of any type (doc, zip, mp3, etc), as well as create groups for up to 200,000 people or channels for broadcasting to unlimited audiences. You can write to your phone contacts and find people by their usernames. As a result, Telegram is like SMS and email combined — and can take care of all your personal or business messaging needs. In addition to this, we support end-to-end encrypted voice and video calls, as well as voice chats in groups for thousands of participants.

-
-

Follow our Tips Channel to learn more about Telegram features.

-
-

Q: Who is Telegram for?

-

Telegram is for everyone who wants fast and reliable messaging and calls. Business users and small teams may like the large groups, usernames, desktop apps and powerful file sharing options.

-

Since Telegram groups can have up to 200,000 members, we support replies, mentions and hashtags that help maintain order and keep communication in large communities efficient. You can appoint admins with advanced tools to help these communities prosper in peace. Public groups can be joined by anyone and are powerful platforms for discussions and collecting feedback.

-

In case you're more into pictures, Telegram has animated gif search, a state of the art photo editor, and an open sticker platform (find some cool stickers here or here). What's more, there is no need to worry about disk space on your device. With Telegram's cloud support and cache management options, Telegram can take up nearly zero space on your phone.

-

Those looking for extra privacy should check out our advanced settings and rather revolutionary policy. And if you want secrecy, try our device-specific Secret Chats with self-destructing messages, photos, and videos — and lock your app with an additional passcode.

-
-

We keep evolving — check out our Brief History of Telegram and follow us on twitter and Telegram to stay in touch.

-
-

Q: How is Telegram different from WhatsApp?

-

Unlike WhatsApp, Telegram is a cloud-based messenger with seamless sync. As a result, you can access your messages from several devices at once, including tablets and computers, and share an unlimited number of photos, videos and files (doc, zip, mp3, etc.) of up to 2 GB each.

-

Telegram needs less than 100 MB on your device – you can keep all your media in the cloud without deleting things – simply clear your cache to free up space.

-

Thanks to Telegram's multi-data center infrastructure and encryption, is faster and way more secure. On top of that, private messaging on Telegram is free and will stay free — no ads, no subscription fees, forever.

-

Telegram's API and code is open, and developers are welcome to create their own Telegram apps. We also have a Bot API, a platform for developers that allows anyone to easily build specialized tools for Telegram, integrate any services, and even accept payments from users around the world.

-

And that's just the tip of the iceberg.

-
-

Follow our Tips Channel to learn more about Telegram features.

-
-

Q: How old is Telegram?

-

Telegram for iOS was launched on August 14, 2013. The alpha version of Telegram for Android officially launched on October 20, 2013. More and more Telegram clients appear, built by independent developers using Telegram's open platform.

-

Q: Which devices can I use?

-

You can use Telegram on smartphones, tablets, and even computers. We have apps for iOS (9.0 and above), Android (4.1 and up), a native macOS app and a universal desktop app for Windows, macOS, and Linux. Telegram Web can also help to quickly do something on the go.

-
-

You can log in to Telegram from as many of your devices as you like — all at the same time. Just use your main mobile phone number to log in everywhere, your cloud chats will sync instantly.

-
-

The Telegram API is open for developers, should you want to build your own applications for other platforms.

-

Q: Who are the people behind Telegram?

-

Telegram is supported by Pavel Durov and his brother Nikolai. Pavel supports Telegram financially and ideologically while Nikolai's input is technological. To make Telegram possible, Nikolai developed a unique custom data protocol, which is open, secure and optimized for work with multiple data-centers. As a result, Telegram combines security, reliability and speed on any network.

-
-

See also: articles about Telegram

-
-

Q: Where is Telegram based?

-

The Telegram development team is based in Dubai.

-

Most of the developers behind Telegram originally come from St. Petersburg, the city famous for its unprecedented number of highly skilled engineers. The Telegram team had to leave Russia due to local IT regulations and has tried a number of locations as its base, including Berlin, London and Singapore. We’re currently happy with Dubai, although are ready to relocate again if local regulations change.

-

Q: Will you have ads in my private chats and groups? Or sell my data? Or steal my beloved and enslave my children?

-

No. See this post for details.

-

Q: How are you going to make money out of this?

-

We believe in fast and secure messaging that is also 100% free.

-

Our founder and CEO Pavel Durov, who financed Telegram throughout most of its history, has outlined a strategy to make Telegram sustainable in this post.

-

While Telegram will introduce monetization in 2021 to pay for the infrastructure and developer salaries, making profits will never be an end-goal for us.

-

Q: What are your thoughts on internet privacy?

-

We think that the two most important components of Internet privacy should be:

-
    -
  1. Protecting your private conversations from snooping third parties, such as officials, employers, etc.
  2. -
  3. Protecting your personal data from third parties, such as marketers, advertisers, etc.
  4. -
-

Telegram's aim is to create a truly free messenger, with a revolutionary privacy policy.

-

Q: What about GDPR?

-

The General Data Protection Regulation (GDPR) came into force in Europe on May 25, 2018. Since taking back our right to privacy was the reason we made Telegram, there wasn't much we had to change. We don’t use your data for ad targeting, we don’t sell it to others, and we're not part of any mafia family “family of companies.”

-

Telegram only keeps the information it needs to function as a feature-rich cloud service. For example, your cloud chats – so that you can access them from any devices without using third-party backups, or your contacts – so that you can rely on your existing social graph when messaging people on Telegram. Please see our Privacy Policy for more information.

-

You can use @GDPRbot to:

-
    -
  • Request a copy of all your data that Telegram stores.
  • -
  • Contact us about Data Privacy.
  • -
-

Q: There's illegal content on Telegram. How do I take it down?

-

All Telegram chats and group chats are private amongst their participants. We do not process any requests related to them.

-

But sticker sets, channels, and bots on Telegram are publicly available. If you find sticker sets or bots on Telegram that you think are illegal, please ping us at abuse@telegram.org.

-

You can also use the 'report' buttons right inside our apps, see this post on our official @ISISwatch channel for details.

-
-

Note: If a scammer is pretending to be you, contact @NoToScam

-
-

Q: A bot or channel is infringing on my copyright. What do I do?

-

All Telegram chats and group chats are private amongst their participants. We do not process any requests related to them. But sticker sets, channels, and bots on Telegram are publicly available.

-

If you see a bot, channel, or sticker set that is infringing on your copyright, kindly submit a complaint to dmca@telegram.org. Please note that such requests should only be submitted by the copyright owner or an agent authorized to act on the owner’s behalf.

-

Q: Wait! 0_o Do you process take-down requests from third parties?

-

Our mission is to provide a secure means of communication that works everywhere on the planet. To do this in the places where it is most needed (and to continue distributing Telegram through the App Store and Google Play), we have to process legitimate requests to take down illegal public content (e.g., sticker sets, bots, and channels) within the app. For example, we can take down sticker sets that violate intellectual property rights or porn bots.

-

User-uploaded stickers sets, channels, and bots by third-party developers are not part of the core Telegram UI. Whenever we receive a complaint at abuse@telegram.org or dmca@telegram.org regarding the legality of public content, we perform the necessary legal checks and take it down when deemed appropriate.

-

Please note that this does not apply to local restrictions on freedom of speech. For example, if criticizing the government is illegal in some country, Telegram won't be a part of such politically motivated censorship. This goes against our founders' principles. While we do block terrorist (e.g. ISIS-related) bots and channels, we will not block anybody who peacefully expresses alternative opinions.

-

Q: My bot or sticker set was banned unfairly, what do I do?

-

If you think we banned your bot, channel, or sticker set for no apparent reasons, drop us a line at abuse@telegram.org.

-

Q: Do you process data requests?

-

Secret chats use end-to-end encryption, thanks to which we don't have any data to disclose.

-

To protect the data that is not covered by end-to-end encryption, Telegram uses a distributed infrastructure. Cloud chat data is stored in multiple data centers around the globe that are controlled by different legal entities spread across different jurisdictions. The relevant decryption keys are split into parts and are never kept in the same place as the data they protect. As a result, several court orders from different jurisdictions are required to force us to give up any data.

-

Thanks to this structure, we can ensure that no single government or block of like-minded countries can intrude on people's privacy and freedom of expression. Telegram can be forced to give up data only if an issue is grave and universal enough to pass the scrutiny of several different legal systems around the world.

-

To this day, we have disclosed 0 bytes of user data to third parties, including governments.

-

Telegram Basics

-
-

Follow our Tips Channel to learn more about Telegram features.

-
-

Q: Who can I write to?

-

You can write to people who are in your phone contacts and have Telegram. Another way of contacting people is to type their Telegram username into the search field – you don't need to know their phone number to do this.

-

Q: Who can contact me?

-

People can contact you on Telegram if they know your phone number or if you message them first.

-

If they don't know your phone number, they can find you in these cases:

-
    -
  • When you both are members of the same group.
  • -
  • If you set a public username. Others can use Global Search and find you by your username.
  • -
  • If you opt-in to appear in the People Nearby section (this is turned off by default).
  • -
-

Q: How do I know who in my contacts has Telegram?

-

Your contacts, who have Telegram, are shown at the top of your Contacts. They also have pictures.

-

Q: How do I invite my friends?

-

iOS: The basic invitations are simple SMS messages. They will be charged as standard outgoing SMS by your carrier (unless sent via iMessage). Naturally, you have other options to bring your friends here. Try sending them a download link via any other messaging service: email, Facebook, WhatsApp, an actual telegram — you name it. The link: https://telegram.org/dl/

-

Android: Open the app menu (swipe right in chat list) > Invite Friends. Then choose an application via which you would like to send out invitations.

-
-

You can give your friends a t.me link with your username so that they can easily find you on Telegram even if they don't have your phone number.

-
-

Q: What do the check marks mean?

-

One check — message delivered to the Telegram cloud and your friend has been notified if he allows notifications.
Two checks — message read (your friend opened Telegram and opened the conversation with the message).

-

We don't have a 'delivered to device' status for messages because Telegram can run on as many devices as you want. So which particular one would that check mean?

-

Q: Can I hide my ‘last seen’ time?

-

You can choose who sees this info in Privacy and Security settings.

-

Remember that you won't see Last Seen timestamps for people with whom you don't share your own. You will, however, see an approximate last seen value. This keeps stalkers away but makes it possible to understand whether a person is reachable over Telegram. There are four possible approximate values:

-
    -
  • Last seen recently — covers anything between 1 second and 2-3 days
  • -
  • Last seen within a week — between 2-3 and seven days
  • -
  • Last seen within a month — between 6-7 days and a month
  • -
  • Last seen a long time ago — more than a month (this is also always shown to blocked users)
  • -
-

Q: Who can see me 'online'?

-

The last seen rules apply to your online status as well. People can only see you online if you're sharing your last seen status with them.

-

There are some exceptions because sometimes it is obvious that you are online. Regardless of the last seen settings, people will see you online for a brief period (~30 seconds) if you do the following:

-
    -
  • Send them a message in a one-on-one chat or in a group where you both are members.
  • -
  • Read a message they sent you in a one-on-one chat.
  • -
  • Broadcast a “typing…” status to their chat with you or to a group where you both are members.
  • -
-

If you're not sharing your last seen timestamp with someone and don't do anything of the above, they'll never see you online. Another way of achieving this is to block that person.

-

Q: What is People Nearby?

-

People Nearby is an optional feature that allows Telegram users to explore local groups, find friends to chat with in their area, or quickly exchange contacts with people who are close.

-

You can find it in Contacts > Find People Nearby, as well as directly in the side menu on Android.

-

While you have the People Nearby section open on your screen, people who are very close will be able to see you there. If you don't open the section, others will never see you in 'People Nearby'.

-

You can also choose to permanently add your profile to the list of nearby people by tapping Make Myself Visible. After becoming visible, you can remove your profile from the list at any time by tapping Stop Showing Me.

-
-

Note: People Nearby is never turned on by default – users must manually enable it. If you are receiving messages from someone you don't know, see Q: Who can contact me?

-
-

Q: Can I delete my messages?

-

Yes. You can always delete any messages you sent or received for both sides in any one-on-one conversation (in groups, it's still your own messages only). You can also clear the entire chat history on both ends. On Telegram, deleted messages do not leave a mark in the chat.

-
- -
- -

Together with privacy settings for forwarded messages, this makes exchanging Telegram messages similar to talking face to face (without a tape recorder). As a result, users no longer need to worry about the data accumulating in their chats over the years. Both parties in a conversation have full control over what does and what doesn't belong to their online identity.

-

Q: Can I make calls via Telegram?

-

Yes! You can make end-to-end encrypted Voice Calls and Video Calls.

-

If you want more participants, try starting a Voice Chat in one of the groups you created. Voice Chats add a live layer of ephemeral talk to the group. They can be used as virtual office spaces for teams or informal lounges for any community. While Voice Chats are not group calls, they can achieve similar goals.

-

Q: How can I use emoticons?

-

Type one word in your input field to get relevant emoji suggestions. You can also type “:” followed by any keyword to open emoji search – like :heart.

-

You can suggest missing keywords for emoji in your language using this interface (this will open suggestions for English, don't forget to change to your language in the left menu).

-

Groups and Channels

-

Q: What makes Telegram groups cool?

-

Telegram groups can have up to 200,000 members each and are extremely powerful communication tools. Here are a few key features that make them stand out in the messaging world:

-

Unified history
Edit your messages after posting, delete them so that they disappear for everyone.

-

Cross-platform availability
Access your messages anytime, from any number of your mobile or desktop devices.

-

Instant search
Find the message you're looking for, even among millions. Filter by sender to make searching easier.

-

Replies, mentions, hashtags
Easily trace a conversation and keep communication efficient, no matter the group size.

-

Smart notifications
Mute the group to get notifications only when people mention you or reply to your messages.

-

Pinned messages
You can pin any message to be displayed at the top of the chat screen. All members will get a notification — even if they muted ordinary messages from your group.

-

Moderation tools
Appoint administrators that can mass-delete messages, control membership, and pin important messages. Define their admin privileges with granular precision.

-

Group permissions
Set default permissions to restrict all members from posting specific kinds of content. Or even restrict members from sending messages altogether – and let the admins chat amongst themselves while everybody else is watching.

-

File sharing
Send and receive files of any type, up to 2 GB in size each, access them instantly on your other devices.

-

Public groups
Get a short link for your group and make it public, like t.me/publictestgroup. This way, anybody can view the group's entire chat history and join to post messages.

-

Customization via bots
Create custom tools for any specific needs using our Bot API and Inline Bots.

-

Q: What's the difference between groups and channels?

-

Telegram groups are ideal for sharing stuff with friends and family or collaboration in small teams. But groups can also grow very large and support communities of up to 200,000 members. You can make any group public, toggle persistent history to control whether or not new members have access to earlier messages and appoint administrators with granular privileges. You can also pin important messages to the top of the screen so that all members can see them, including those who have just joined.

-

Channels are a tool for broadcasting messages to large audiences. In fact, a channel can have an unlimited number of subscribers. When you post in a channel, the message is signed with the channel's name and photo and not your own. Each message in a channel has a view counter that gets updated when the message is viewed, including its forwarded copies.

-
-

Read more about channels in the Channels FAQ »

-
-

Q: How do I create a group?

-

iOS: Start a new message (tap the icon in the top right corner in Chats) > 'New Group'.
Android: Tap the circular pencil icon in the chat list > 'New Group'.
Telegram Desktop: Click the menu button in the top left corner > 'New Group'.

-

Q: Can I assign administrators?

-

You can add administrators to help you manage your group and define their privileges with granular precision.

-

iOS: Go to Group Info (tap the photo in the top right corner on the group‘s chat screen) > Edit > Administrators.
Android: Go to Group Info (tap the name in the header) > the pencil icon (in the top right corner) > Administrators.
Telegram Desktop: When in the group, click '…' in the top right corner > Manage group > Administrators.

-

Q: How do I add more members? What's an invite link?

-

You can add your contacts, or using search by username.

-

It is easy to migrate existing groups to Telegram by sending people an invite link. To create an invite link, go to Group Info > Add Member > Invite to Group via Link.

-

Anyone who has Telegram installed will be able to join your group by following this link. If you choose to revoke the link, it will stop working immediately.

-
-

Read more about invite links in our blog »

-
-

Usernames and t.me

-

Q: What are usernames? How do I get one?

-

You can set up a public username on Telegram. It then becomes possible for other users to find you by that username — you will appear in contacts search under 'global results'. Please note that people who find you will be able to send you messages, even if they don't know your number. If you are not comfortable with this, we advise against setting up a username in Telegram.

-

You can set up a username in Settings and use the universal search box in the chat list to search for chats, messages, and usernames.

-

Q: How does t.me work?

-

Once you've set up a username, you can give people a t.me/username link. Opening that link on their phone will automatically fire up their Telegram app and open a chat with you. You can share username links with friends, write them on business cards or put them up on your website.

-

This way people can contact you on Telegram without knowing your phone number.

-

Q: What can I use as my username?

-

You can use a-z, 0-9 and underscores. Usernames are case-insensitive, but Telegram will store your capitalization preferences (e.g. Telegram and TeleGram is the same user). The username must be at least five characters long.

-

Q: Do I need a username?

-

You don't have to get one. Remember that Telegram usernames are public and choosing a username on Telegram makes it possible for people to find you in global search and send you messages even if they don't have your number. If you are not comfortable with this, we advise against setting up a username.

-

Q: If someone finds me by username, messages and I reply — will they know my number?

-

No. Neither party will see another's phone number (unless this is permitted by your privacy settings). This is similar to the case when you message a person who you've met in a Telegram group.

-

Q: How do I delete my username?

-

Go to Settings and save an empty username. This will remove your username; people will no longer be able to find you via search. This will not affect existing conversations.

-

Q: What do I do if my username is taken?

-

Telegram usernames are distributed on a first come — first serve basis.

-

We understand that certain usernames are part of an online identity for some of us. If your desired username is already taken, we will be happy to help you acquire it for your account or channel, provided that you have that same username on at least two of these services: Facebook, Twitter, Instagram.

-

Due to the fact that one account can register multiple bot and channel usernames, we reserve the right to recall usernames assigned to unused bots and channels, as well as openly squatted usernames.

-

To request a username, contact @Username_bot.

-

Q: What if someone is pretending to be me?

-

If a scammer is pretending to be you, please contact @NoToScam.

-

Security

-
-

If you are an advanced user, you may find our FAQ for the Technically Inclined useful as well.

-
-

Q: How secure is Telegram?

-

Telegram is more secure than mass market messengers like WhatsApp and Line. We are based on the MTProto protocol (see description and advanced FAQ), built upon time-tested algorithms to make security compatible with high-speed delivery and reliability on weak connections. We are continuously working with the community to improve the security of our protocol and clients.

-

Q: What if I’m more paranoid than your regular user?

-

We've got you covered. Telegram’s special secret chats use end-to-end encryption, leave no trace on our servers, support self-destructing messages and don’t allow forwarding. On top of this, secret chats are not part of the Telegram cloud and can only be accessed on their devices of origin.

-

Q: So how do you encrypt data?

-

We support two layers of secure encryption. Server-client encryption is used in Cloud Chats (private and group chats), Secret Chats use an additional layer of client-client encryption. All data, regardless of type, is encrypted in the same way — be it text, media or files.

-

Our encryption is based on 256-bit symmetric AES encryption, 2048-bit RSA encryption, and Diffie–Hellman secure key exchange. You can find more info in the Advanced FAQ.

-
-

See also: Do you process data requests?

-
-

Q: Why should I trust you?

-

Telegram is open, anyone can check our source code, protocol and API, see how everything works and make an informed decision. Telegram supports verifiable builds, which allow experts to independently verify that our code published on GitHub is the exact same code that is used to build the apps you download from App Store or Google Play.

-

We welcome security experts to audit our system and appreciate any feedback at security@telegram.org.

-

On top of that, Telegram's primary focus is not to bring a profit, so commercial interests will never interfere with our mission.

-
-

See also: articles about Telegram

-
-

Q: Do I need to trust Telegram for this to be secure?

-

When it comes to secret chats, you don't — just make sure that the visualized key of your secret chat matches the one in your friend's secret chat settings. More about this below.

-

Q: What if my hacker friend says they could decipher Telegram messages?

-

Anyone who claims that Telegram messages can be deciphered is welcome to prove that claim in our competition and win $300,000. You can check out the Cracking Contest Description to learn more.

-

Any comments on Telegram's security are welcome at security@telegram.org. All submissions which result in a change of code or configuration are eligible for bounties, ranging from $100 to $100,000 or more, depending on the severity of the issue. Please note that we can not offer bounties for issues that are disclosed to the public before they are fixed.

-

Q: Can Telegram protect me against everything?

-

Telegram can help when it comes to data transfer and secure communication. This means that all data (including media and files) that you send and receive via Telegram cannot be deciphered when intercepted by your internet service provider, owners of Wi-Fi routers you connect to, or other third parties.

-

But please remember that we cannot protect you from your own mother if she takes your unlocked phone without a passcode. Or from your IT-department if they access your computer at work. Or from any other people that get physical or root access to your phones or computers running Telegram.

-

If you have reasons to worry about your personal security, we strongly recommend using only Secret Chats in official or at least verifiable open-source apps for sensitive information, preferably with a self-destruct timer. We also recommend enabling 2-Step Verification and setting up a strong passcode to lock your app, you will find both options in Settings > Privacy and Security.

-

Q: How does 2-Step Verification work?

-

Logging in with an SMS code is an industry standard in messaging, but if you're looking for more security or have reasons to doubt your mobile carrier or government, we recommend protecting your cloud chats with an additional password.

-

You can do this in Settings > Privacy and Security > 2-Step Verification. Once enabled, you will need both an SMS code and a password to log in. You can also set up a recovery email address that will help regain access, should you forget your password. If you do so, please remember that it's important that the recovery email account is also protected with a strong password and 2-Step Verification when possible.

-

Check this out for tips on creating a strong password that is easy to remember.

-

Q: Why can jailbroken and rooted devices be dangerous?

-

Using a rooted or jailbroken device makes it easier for a potential attacker to gain full administrative control over your device — root access.

-

A user with root access can easily bypass security features built into the operating system, read process memory or access restricted areas, such as the internal storage. Once an attacker has root access, any efforts to mitigate threats become futile. No application can be called safe under these circumstances, no matter how strong the encryption.

-

Secret Chats

-

Q: How are secret chats different?

-

Secret chats are meant for people who want more secrecy than the average fella. All messages in secret chats use end-to-end encryption. This means only you and the recipient can read those messages — nobody else can decipher them, including us here at Telegram (more on this here). On top of this, Messages cannot be forwarded from secret chats. And when you delete messages on your side of the conversation, the app on the other side of the secret chat will be ordered to delete them as well.

-

You can order your messages, photos, videos and files to self-destruct in a set amount of time after they have been read or opened by the recipient. The message will then disappear from both your and your friend's devices.

-

All secret chats in Telegram are device-specific and are not part of the Telegram cloud. This means you can only access messages in a secret chat from their device of origin. They are safe for as long as your device is safe in your pocket.

-

Q: How do I start a secret chat?

-

Open the profile of the user you want to contact. Tap on ‘…’, then ‘Start Secret Chat’.

-

Remember that Telegram secret chats are device-specific. If you start a secret chat with a friend on one of your devices, this chat will only be available on that device. If you log out, you will lose all your secret chats. You can create as many different secret chats with the same contact as you like.

-

Q: How do self-destructing messages work?

-

The Self-Destruct Timer is available for all messages in Secret Chats and for media in private cloud chats.

-

To set the timer, simply tap the clock icon (in the input field on iOS, top bar on Android), and then choose the desired time limit. The clock starts ticking the moment the message is displayed on the recipient's screen (gets two check marks). As soon as the time runs out, the message disappears from both devices. We will try to send a notification if a screenshot is taken.

-

Please note that the timer in Secret Chats only applies to messages that were sent after the timer was set. It has no effect on earlier messages.

-

Q: Can I be certain that my conversation partner doesn't take a screenshot?

-

Unfortunately, there is no bulletproof way of detecting screenshots on certain systems (most notably, some Android and Windows Phone devices). We will make every effort to alert you about screenshots taken in your Secret Chats, but it may still be possible to bypass such notifications and take screenshots silently. We advise to share sensitive information only with people you trust. After all, nobody can stop a person from taking a picture of their screen with a different device or an old school camera.

-

Q: What is this 'Encryption Key' thing?

-

When a secret chat is created, the participating devices exchange encryption keys using the so-called Diffie-Hellman key exchange. After the secure end-to-end connection has been established, we generate a picture that visualizes the encryption key for your chat. You can then compare this image with the one your friend has — if the two images are the same, you can be sure that the secret chat is secure, and no man-in-the-middle attack can succeed.

-

Newer versions of Telegram apps will show a larger picture along with a textual representation of the key (this is not the key itself, of course!) when both participants are using an updated app.

-

Always compare visualizations using a channel that is known to be secure — it's safest if you do this in person, in an offline meeting with the conversation partner.

-

Q: Why not just make all chats 'secret'?

-

All Telegram messages are always securely encrypted. Messages in Secret Chats use client-client encryption, while Cloud Chats use client-server/server-client encryption and are stored encrypted in the Telegram Cloud (more here). This enables your cloud messages to be both secure and immediately accessible from any of your devices – even if you lose your device altogether.

-

The problem of restoring access to your chat history on a newly connected device (e.g. when you lose your phone) does not have an elegant solution in the end-to-end encryption paradigm. At the same time, reliable backups are an essential feature for any mass-market messenger. To solve this problem, some applications (like Whatsapp and Viber) allow decryptable backups that put their users' privacy at risk – even if they do not enable backups themselves. Other apps ignore the need for backups altogether and leave their users vulnerable to data loss.

-

We opted for a third approach by offering two distinct types of chats. Telegram disables default system backups and provides all users with an integrated security-focused backup solution in the form of Cloud Chats. Meanwhile, the separate entity of Secret Chats gives you full control over the data you do not want to be stored.

-

This allows Telegram to be widely adopted in broad circles, not just by activists and dissidents, so that the simple fact of using Telegram does not mark users as targets for heightened surveillance in certain countries. We are convinced that the separation of conversations into Cloud and Secret chats represents the most secure solution currently possible for a massively popular messaging application.

-
-

See also: Why Telegram isn't End-to-End Encrypted “by Default”

-
-

Your Account

-

Q: Who can see my phone number?

-

On Telegram, you can send messages in private chats and groups without making your phone number visible. By default, your number is only visible to people who you've added to your address book as contacts. You can further modify this in Settings > Privacy and Security > Phone Number.

-
-

Note that people will always see your number if they know it already and saved it in their address book.

-
-

Q: I have a new phone number, what do I do?

-

Each phone number is a separate account on Telegram. You have several options if you are using multiple phone numbers:

-
    -
  • If you will no longer use the old number (e.g., you moved to a new country or changed your number for good), simply go to Settings and change the number connected to your Telegram account to the new number. Important: make sure you have access to your connected phone number – otherwise you risk losing access to your account.
  • -
  • If you will use the new number for a limited time (e.g., you're on a trip or vacation), there's no need to do anything.
  • -
  • If you want to keep using both numbers (e.g., you have a work phone and personal phone), choose one as your Telegram number. You may create another Telegram account on the second number as well, for example, if you want to keep work and personal chats separated. It is possible to log in to one Telegram app with up to 3 different accounts at once.
  • -
-

Q: How do I log out?

-

Most users don't need to log out of Telegram:

-
    -
  • You can use Telegram on many devices at the same time. Just use the same phone number to log in on all devices.
  • -
  • You can go to Settings > Data and Storage > Storage Usage> Clear cache to free up space on your device without logging out.
  • -
  • If you use Telegram with multiple phone numbers, you can switch between accounts without logging out.
  • -
  • If you use Telegram on a shared device, you can set up a passcode in Settings > Privacy and Security to make sure only you have access to your account.
  • -
-

If you do want to log out for some reason, here's how you do that:

-

iOS: Go to Settings > Edit > Log out.
Android, Telegram Desktop: Go to Settings > … (in the top right corner) > Log out.

-

If you log out, you will keep all your cloud messages. However, you will lose all your Secret Chats and all messages inside those secret chats when you log out.

-
-

Note that logging out does not trigger remote deletion of your secret chat messages on your partner's device — to do that, choose 'Clear History' first.

-
-

Q: How do I change my phone number?

-

You can change your number in Telegram and keep everything, including all your contacts, messages, and media from the Telegram cloud, as well as all your Secret Chats on all devices.

-

To change your number, go to Settings, then tap on your phone number (just above the username), then 'Change Number'. If you already have a different Telegram account on the target number, you'll need to delete that account first.

-

Q: How do I delete my account?

-

If you would like to delete your account, you can do this on the deactivation page. Deleting your account permanently removes all your messages and contacts. All groups and channels that you've created are orphaned and left without a creator but admins retain their rights.

-

This action must be confirmed via your Telegram account and cannot be undone.

-
-

We recommend using a non-mobile browser for this process.
Note that you'll receive the code via Telegram, not SMS.

-
-

Q: What happens if I delete my account?

-

As was just mentioned above, all your data will be flushed from our system: all messages, groups, and contacts associated with your account will be deleted. That said, your contacts will still be able to chat in the groups that you have created, and they will still have their copy of the messages you sent them. So if you want to send messages that can vanish without a trace, try using our self-destruct timer instead.

-

Termination of a Telegram account is irreversible. If you sign up again, you will appear as a new user and will not get your history, contacts or groups back. People, who have your phone number in their contacts, will be notified. The new user will be displayed as a separate conversation in their messages list and their conversation history with this new user will be empty.

-

Q: How does account self-destruction work?

-

Telegram is not a commercial organization, and we value our disk space greatly. If you stop using Telegram and don't come online for at least six months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud. You can change the exact period after which your inactive account will self-destruct in Settings.

-

Q: My phone was stolen, what do I do?

-

First of all, sorry about your phone. Unfortunately, the phone number is the only way for us to identify a Telegram user at the moment. We don't collect additional information about you, so whoever has the number, has the account. This means we can't help you unless you have access either to the phone number or to Telegram itself on any of your devices.

-
I have access to Telegram on another device
-
    -
  1. Go to Telegram Settings > Privacy and Security and turn on Two-Step Verification. This way the phone number alone will not be enough to log in to your account.
  2. -
  3. Go to Settings > Devices (or Privacy & Security > Active Sessions) and terminate your Telegram session on the old device. Whoever has your phone will not be able to log in again, since they don't know your password.
  4. -
  5. Contact your phone provider, so that they block your old SIM and issue a new one with your number.
  6. -
  7. If you decide to switch to a new phone number, don't forget to go to Settings, tap on your phone number and change your Telegram number to the new one.
  8. -
-
I don't have access to Telegram on any other devices
-
    -
  1. First and foremost, you need to contact your phone provider, so that they block your old SIM and issue a new one with your number.
  2. -
  3. Wait till you receive your new SIM with the old number, log in to Telegram, then go to Settings > Devices (or Privacy & Security > Active Sessions) and terminate your Telegram session on the old device.
  4. -
-
Removing sensitive data
-

Common thieves usually throw out the SIM card immediately (the phone is harder to locate this way), then wipe the devices and sell them, so there isn't much risk for the data in case of regular petty theft. But if you have reasons to worry about the data on the device and are unable to log out the other device, it is best that you wipe it remotely. You can read more about it here: Apple iOS, Android. Unfortunately, this requires you to have prepared in advance for this scenario.

-

You can delete your Telegram account if you are logged in on at least one of your other devices (mobile or desktop). Note that inactive Telegram accounts self-destruct automatically after a period of time — 6 months being the default setting.

-

Bots

-
-

If you're a developer, you may find our Bots FAQ more useful.

-
-

Q: What are bots?

-

Bots are like small programs that run right inside Telegram. They are made by third-party developers using the Telegram Bot API.

-

Q: How do I create a bot?

-

Creating Telegram bots is super-easy, but you will need at least some skills in computer programming. If you're sure you're up to it, our Introduction for Developers is a good place to start.

-

Unfortunately, there are no out-of-the-box ways to create a working bot if you are not a developer. But we're sure you'll soon find plenty of bots created by other people to play with.

-

Q: A bot is sending me messages, how do I make it stop?

-

If you don't want a bot to send you messages, feel free to block it – same as you would block a human user. Some Telegram clients have a 'Stop Bot' button right in the bot's profile.

-

That said, most bot developers offer commands that silence the bot, check its /help for clues.

-

Q: Are bots safe?

-

Yes. Bots are no different from human users that you meet in groups for example. They can see your public name, username, and profile pictures, and they can see messages you send to them, that's it. They can't access your last seen status and don't see your phone number (unless you decide to give it to them yourself).

-

Naturally, any bot should be treated as a stranger — don't give them your passwords, Telegram codes or bank account numbers, even if they ask nicely. Also, be careful when opening files sent by bots, same as you would deal with ordinary humans. Example: If a bot sent us a file called OpenMe.exe, we probably wouldn't open it.

-

Q: If I add a bot to my group, can it read my messages?

-

Bots can work in two modes when you add them to groups. By default, bots only see messages that are meant for them. In this case, you'll see 'has no access to messages' in the group members list next to the bot.

-

Some bots need more information to work, so developers may disable the privacy mode. In this case, the bot will see all messages sent to the group, and you will see 'has access to messages' in the members list next to the bot.

-

Learn more about privacy mode for bots »

-

If your group contains very sensitive information, maybe it's better to avoid adding bots you don't trust 100%.

-

Q: Are bots made by Telegram?

-

No. While we have some official bots for specific purposes (like @gif or @GDPRbot), we don't usually make bots. Bots are made by third-party developers using the Telegram Bot API and platform.

-

Q: Where can I find more bots?

-

There is no official store at the moment, so you'll have to ask your friends or search the web for now. We're pretty sure you'll find some bots to play with.

-

Deeper questions

-

Q: Can I get Telegram's server-side code?

-

All Telegram client apps are fully open source. We offer verifiable builds both for iOS and Android – this technology allows to independently verify that the application you download from the app stores was built using the exact same code that we publish.

-

By contrast, publishing the server code doesn’t provide security guarantees neither for Secret Chats nor for Cloud Chats. This is because – unlike with the client-side code – there’s no way to verify that the same code is run on the servers.

-

As for Secret Chats, you don’t need the server-side code to check their integrity – the point of end-to-end encryption is that it must be solid regardless of how the servers function.

-
-

In a post on his channel, Pavel Durov explained why Telegram hasn't published the server code, even as a publicity stunt.

-
-

The encryption and API used on Telegram's servers are fully documented and open for review by security experts. We welcome any comments at security@telegram.org

-

Q: Can I run Telegram using my own server?

-

Our architecture does not support federation yet. Telegram is a unified cloud service, so creating forks where two users might end up on two different Telegram clouds is unacceptable. To enable you to run your own Telegram server while retaining both speed and security is a task in itself. At the moment, we are undecided on whether or not Telegram should go in this direction.

-

Q: Can I use the Telegram API?

-

Yes. Developers for all platforms are welcome to use our protocol, API and even source code. Check out the Getting started section of the docs.

-
-

Don't forget about our Bot API that lets you build cool stuff on our platform.

-
-

Q: Do you have a Privacy Policy?

-

Sure. Check this out.

-

Q: What does the iOS privacy sheet mean?

-

Apple created privacy sheets to inform users about what data apps may collect, but information there is vague and can be misleading. You can see a detailed explanation of Telegram's sheet here.

-

Q: Why do you have two apps in the Mac App Store?

-

One is our app for macOS, the other is Telegram Lite, the macOS version of our multi-platform client. Both apps are official. Both started out as unofficial applications by two different developers and vary in design and functionality.

-

Telegram for macOS supports many platform-specific features, such as the MacBook Pro Touch Bar, gesture navigation, integration with the Mac's Share menu and more. It has every feature from the iOS version of the app including Secret Chats.

-

Telegram Lite is a lightning-fast app, optimized for work-related tasks and handling large communities. It offers a three-column interface, perfect for multitasking and quick access to media, files and links shared in your chats. This app can also be used to export your Telegram data and chats.

-

Q: Can I translate Telegram?

-

Telegram is officially available in English, Spanish, German, Dutch, Italian, French, Arabic, Portuguese, Korean, Malay, Russian and Ukrainian on most platforms, and we are gradually expanding the list of languages built into the apps.

-

If you don’t like how a specific element in Telegram's interface is translated in your language, or would like to help us maintain the translation, check out our localization platform. Everyone can suggest translations and vote for the best ones, making Telegram localization a community-driven effort.

-

If you're looking to go beyond suggestions for individual phrases and would like to help us maintain the official translation to your language on a continuous basis, you can contact @TelegramAuditions. Please include a hashtag with the English name of your language (e.g. #Albanian) and a few links to phrases on this platform with your translation suggestions or comments. Be sure to read the Style Guide carefully before you apply.

-

Q: Can I help?

-

Yes, we are always looking for volunteers to help us with user support. If you would be interested in answering questions about Telegram to users from your country, contact our auditions account.

-

Before you apply, please check out the Telegram Support Initiative.

-

Passport

-

Telegram Passport is a unified authorization method for services that require personal identification. With Telegram Passport, you can upload your documents once, then instantly share your data with services that require real-world ID (finance, ICOs, etc.).

-

Your identity documents and personal data will be stored in the Telegram cloud using End-to-End Encryption. To Telegram, this data is just random gibberish, and we have no access to the information you store in your Telegram Passport. When you share data, it goes directly to the recipient.

-
-

You can find more information about Telegram Passport on our blog.

-
-

If you're a developer or owner of a service that requires real-life ID, kindly take a look at this manual. You can also try requesting Telegram Passport data using this page.

-
-

Troubleshooting

-

Login and SMS

-

Please make sure you are entering your mobile phone number in the international format.
I.e.: +(country code)(city or carrier code)(your number)

-

If you are having registration or login problems, please contact us using this form.

-

Getting a code via a phone call

-

For security reasons, login codes dictated via a phone call are only available for accounts that have two-step verification enabled (Settings > Privacy & Security > Two-Step Verification).

-

Please also note that Telegram accounts can only be connected to a mobile number. We currently don't support landline numbers.

-

Getting a code via Telegram

-

If you have recently used one of our apps on another device (it could also be a different app on the same device), we may send the login code via Telegram instead of SMS.

-

To receive such a code, just check Telegram from any of your connected devices. You will find it in the chat with Telegram, a verified profile with a blue check:

-
- -

Login code sent via Telegram

-
- -

WARNING! Please note that getting codes via Telegram should not be considered an alternative to using an up-to-date phone number. In case of a change in numbers, always make sure Telegram is connected to a phone number you control, otherwise you risk losing access to your account forever.

-

Notification problems

-
-

If the tips below don't help, check out this detailed guide on Troubleshooting Notification Issues.

-
-

ANDROID

-
    -
  1. Go to Telegram Settings — Notifications and Sounds, make sure that notifications are ON and Importance is set to “High” or greater.
  2. -
  3. Check whether contact or group is muted.
  4. -
  5. Make sure Google Play Services are installed on your phone.
  6. -
  7. Check notification priority for Telegram in Android settings, it can be called Importance or Behaviour depending on your device.
  8. -
  9. If your phone uses some battery saving software, make sure that Telegram is whitelisted in that application.
  10. -
-
-

NOTE: Huawei and Xiaomi devices have evil task killer services that interfere with the Telegram notification service. For our notifications to work, you need to add Telegram to allowed apps in those devices' security settings. Huawei: Phone Manager App > Protected Apps > Add Telegram to the list. Xiaomi: Services > Security > Permissions > Autostart, find Telegram and enable autostart.

-
-

iOS

-
    -
  1. Go to Telegram Settings — Notifications and Sounds, make sure that notifications are ON in Telegram.
  2. -
  3. Check that notifications are ON in phone Settings.
  4. -
  5. Check, whether contact or group is muted.
  6. -
  7. Shut down Telegram (go to home screen, double tap home button, swipe upwards on Telegram), then go to phone settings, set the alert style for Telegram to NONE. Relaunch Telegram, go to phone settings, set alert style back to banners.
  8. -
-

Problems with contacts

-

If you know your friends have Telegram, but you can't see them — or they appear as numbers instead of names.

-

Android:

-
    -
  1. Make sure you are using the latest version of the app.
  2. -
  3. Relaunch the app (by terminating it from processes list and launching again).
  4. -
  5. Temporarily change the name of the contact in phone contacts (add a few symbols, then change back again).
  6. -
  7. If that didn't help, re-login. Remember that logging out kills your Secret Chats.
  8. -
-

iOS:

-
    -
  1. Force quit the app (double tap home button, then swipe up on Telegram), then relaunch and check if it helped.
  2. -
  3. If that doesn't help, temporarily change the name of the contact in phone contacts (add a few symbols, then change back again).
  4. -
  5. If that doesn’t work, re-login: Settings > Edit > Log Out. Remember that logging out kills all your Secret Chats. Then log in again.
  6. -
-

Deleting contacts on Android

-

To delete a contact, open a chat with the person, tap the title in the top area of the chat screen to open their profile, then tap on (⋮) in the top right corner > 'Delete contact'.

-

If you want to delete the contact completely, make sure you also delete them from your phone contacts. Telegram stays in sync and will add the contact back if you don't.

-

Where did my Secret Chat messages go?

-

Secret Chats are established between the two devices they were created on. This means that all those messages are not available in the cloud and cannot be accessed on other devices.

-

Moreover, Secret Chats are also tied to your current login session on the device. If you log out and in again, you will lose all your Secret Chats.

-

Can't send messages to non-contacts

-

When users report unwanted messages from a Telegram account, we apply a limit: Reported accounts can only send messages to people who have their number saved as a contact.

-

This means that if you randomly contact people you don't know and send them annoying messages, you may lose the ability to do so in the future.

-

If you think that this limit was applied to your account wrongly, please visit this page.

-

Telegram uses the camera or microphone in the background!

-

Telegram can use the microphone in the background if you minimize the app when making a call, recording a video, or recording a voice/video message.

-

Permission monitors on Samsung and Xiaomi can inadvertently flag and notify you that Telegram requested access to camera in the background. This happens when the app requests info about the camera — it isn’t using the camera. Unfortunately it may look the same to the Samsung and Xiaomi permission monitors.

-

Camera info is requested by the app when you tap on the attachment button, or start recording a video or a video message. If you do this and quickly close the app, the already initiated request may try to run asynchronously when the app is already in the background, or be sent when the system wakes up the app to show a notification about a new message. In any case, these requests are only for the camera info, the app never uses the camera itself in the background.

-

Anyone can check Telegram’s open source code and confirm that the app is not doing anything behind their back. We also offer reproducible builds that can help you prove that the version you downloaded from App Store or Google Play is built from the exact same source code we publish.

-
-

Telegram Support

-

If you have any other questions, please contact Telegram Support (in Telegram go to Settings — Ask a question). Note that we rely on volunteers for support.

-

If you can't log in to your account, please use this form.

-
-

For media requests, please contact @PressBot on Telegram.

-
-

Twitter?

-

Yep. Follow us! @telegram
Our twitter account in Spanish: @telegram_es
In Italian: @telegram_it
In Korean: @Telegram_kr
In German: @de_telegram
For users from Brazil: @Telegram_br
Our Arabic-speaking users may find @telegram_arabic more interesting.

-

@SmsTelegram, login help on Twitter

-

We have a special account that can help you with login problems, @smstelegram. This account is official. Don't be afraid to DM it the number you use for Telegram, we need this info to investigate issues.

-

Be careful, we don't have any other support accounts on any social media platforms.

-

Facebook or other platforms?

-

If anyone on Facebook or any other platform is telling you they're us, they are not.

-

-
- -
- -
-
-
- - - - - - - diff --git a/data/telegram.org/faq_spam.html b/data/telegram.org/faq_spam.html deleted file mode 100644 index df27b79c21..0000000000 --- a/data/telegram.org/faq_spam.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - Spam FAQ - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
-
-

Spam FAQ

- -
-

This FAQ is for people whose accounts were limited after being reported for spam.
Back to the main FAQ »

-
-

-
-

Q: What happened to my account?

-

When users press the ‘Report spam’ button in a chat, they forward these messages to our team of moderators for review. If the moderators decide that the messages deserved this, the account becomes limited temporarily.

-

This means that if you have been sending unwanted messages to random strangers or posting spam in groups, you lose the ability to do so.

-

Q: So I can't send messages anymore?

-

No, it's not that bad. Limited accounts can send messages to people who have their number saved as a contact. You can also always reply to anyone who messages you first.

-

Q: Why was I reported?

-

Telegram‘s username search is not a tool for making new friends. People usually don’t like it when strangers contact them — so they will report you if they find your messages annoying. Please only contact people if you're sure that they are expecting messages from you. The same applies to adding people to unwanted groups and channels. In addition to this, group admins can also report users who post spam in their groups.

-

Naturally, all such reports are also checked by human moderators. If the messages contain spam, the account will be temporarily limited.

-

Q: What can people report me for?

-

For private messages, it really doesn‘t matter what you send, as long as the receivers find it unwelcome. It could have been a photo, an invite link or a simple ’hello‘. Please only send messages when you are sure people won’t mind getting them.

-

As a general rule, people do mind getting unsolicited advertisements, links, invite links to groups or channels, random photos and, above all, anything related to commerce or online popularity. If you send them something like this, you will be blocked — and everybody else will be happy.

-

Moderators are more lenient when it comes to messages in groups, but anyone who sends spam or unsolicited advertisments will be limited.

-

Q: What do I do now?

-

If this happened to you for the first time (and you are not an industrial scale spammer), most likely your account will be limited for a few days or so. Please wait and consider that people want a peaceful time using our messenger.

-

Repeated offences will result in longer periods of being blocked. If you keep writing unwanted messages to strangers, you may lose the ability to do so forever.

-

Q: I read all of the above, and I‘m certain that I didn’t break any rules!

-

If you are sure that the limit was wrongfully applied to your account, please contact our @SpamBot.

-

Please forgive us for the inconvenience — even the best systems, algorithms and well-trained people can make mistakes sometimes.

-

Q: I know I was wrong, please release me sooner!

-

We're sorry, but this is impossible. We value the inner peace of Telegram users too much.

-

Q: I‘ve just signed up and didn’t send any messages yet, but my account is limited.

-

Some numbers may trigger an overly harsh response from our system, either due to their previous owners‘ activities or due to them being certain virtual/VOIP numbers. We’re sorry if this resulted in your account being limited for no reason.

-

If you think this is your case, please contact @SpamBot and tell it your story.

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