users.getUsers
users.getUsers
Section titled “users.getUsers”No description provided by the pinned schema.
Signature
Section titled “Signature”users.getUsers#0d91a548 id:Vector<InputUser> = Vector<User>;Result type
Section titled “Result type”Vector<User>
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| id | Vector | — | — | No description provided by the pinned schema. |
Python binding
Section titled “Python binding”from miniproto.raw.functions import UsersGetUsersPublic access: miniproto.raw.functions.UsersGetUsers.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.functions import UsersGetUsers
# Naming the raw request class is local only; it performs no I/O or network request.request_type = UsersGetUsersResult family
Section titled “Result family”RPC errors
Section titled “RPC errors”| Code | Error | Description |
|---|---|---|
| 400 | BUSINESS_CONNECTION_NOT_ALLOWED | This method was invoked over a business connection using invokeWithBusinessConnection, but either (1) we’re a user, and users cannot invoke methods over a business connection; (2) we’re a bot, but business mode was disabled in @botfather or (3); we’re a bot, but this method cannot be invoked over a business connection. |
| 400 | CHANNEL_INVALID | The provided channel is invalid. |
| 400 | CHANNEL_MONOFORUM_UNSUPPORTED | Monoforums do not support this feature. |
| 400 | CHANNEL_PRIVATE | You haven’t joined this channel/supergroup. |
| 400 | FROM_MESSAGE_BOT_DISABLED | Bots can’t use fromMessage min constructors. |
| 400 | MSG_ID_INVALID | Invalid message ID provided. |
| 400 | PEER_ID_INVALID | The provided peer id is invalid. |
| 400 | USER_BANNED_IN_CHANNEL | You’re banned from sending messages in supergroups/channels. |
| 401 | AUTH_KEY_UNREGISTERED | The specified authorization key is not registered in the system (for example, a PFS temporary key has expired). |
Accepted types
Section titled “Accepted types”InputUser
Known selected constructors: inputUser, inputUserEmpty, inputUserFromMessage, inputUserSelf
Returned types
Section titled “Returned types”User
Known selected constructors: user, userEmpty
Related methods
Section titled “Related methods”account.changePhone, account.confirmBotConnection, account.getPaidMessagesRevenue, account.toggleNoPaidMessagesException, account.updateConnectedBot, account.updateProfile, account.updateUsername, bots.addPreviewMedia, bots.allowSendMessage, bots.canSendMessage, bots.checkDownloadFileParams, bots.createBot, bots.deletePreviewMedia, bots.editAccessSettings, bots.editPreviewMedia, bots.exportBotToken, bots.getAccessSettings, bots.getAdminedBots, bots.getBotInfo, bots.getBotMenuButton, bots.getBotRecommendations, bots.getPreviewInfo, bots.getPreviewMedias, bots.getRequestedWebViewButton, bots.invokeWebViewCustomMethod, bots.reorderPreviewMedias, bots.reorderUsernames, bots.requestWebViewButton, bots.setBotInfo, bots.setBotMenuButton, bots.setCustomVerification, bots.toggleUserEmojiStatusPermission, bots.toggleUsername, bots.updateStarRefProgram, bots.updateUserEmojiStatus, channels.editAdmin, channels.getAdminLog, channels.getMessageAuthor, channels.inviteToChannel, channels.toggleJoinRequest, contacts.acceptContact, contacts.addContact, contacts.deleteContacts, contacts.importContactToken, contacts.updateContactNote, ephemeral.deleteMessage, ephemeral.editMessage, ephemeral.sendMessage, help.editUserInfo, help.getUserInfo, messages.addChatUser, messages.createChat, messages.deleteChatUser, messages.deleteRevokedExportedChatInvites, messages.editChatAdmin, messages.editChatCreator, messages.getAttachMenuBot, messages.getChatInviteImporters, messages.getCommonChats, messages.getExportedChatInvites, messages.getFutureChatCreatorAfterLeave, messages.getGameHighScores, messages.getInlineBotResults, messages.getInlineGameHighScores, messages.getPersonalChannelHistory, messages.getPreparedInlineMessage, messages.hideChatJoinRequest, messages.prolongWebView, messages.requestEncryption, messages.requestMainWebView, messages.requestSimpleWebView, messages.requestWebView, messages.savePreparedInlineMessage, messages.sendWebViewData, messages.setGameScore, messages.setInlineGameScore, messages.startBot, messages.toggleBotInAttachMenu, payments.botCancelStarsSubscription, payments.connectStarRefBot, payments.getConnectedStarRefBot, payments.getStarsGiftOptions, payments.refundStarsCharge, phone.inviteConferenceCallParticipant, phone.inviteToGroupCall, phone.requestCall, photos.getUserPhotos, photos.updateProfilePhoto, photos.uploadContactProfilePhoto, photos.uploadProfilePhoto, premium.getUserBoosts, stickers.createStickerSet, users.getFullUser, users.getRequirementsToContact, users.getSavedMusic, users.getSavedMusicByID, users.setSecureValueErrors, users.suggestBirthday
Provenance
Section titled “Provenance”- layer: 228
- structural source:
tdlib - canonical schema: https://raw.githubusercontent.com/tdlib/td/refs/heads/master/td/generate/scheme/telegram_api.tl
- prose merge precedence: TDLib → Telegram Desktop → Core JSON
- source note: Canonical structure is the pinned TDLib telegram_api.tl; Layer 228 comes only from the matching Telegram Desktop end-of-file marker; core.telegram.org inputs enrich documentation and RPC error metadata without overriding structure.
Source-diff notes
Section titled “Source-diff notes”- tdlib_vs_core: changed_count=68; core_only_count=1; overlap_count=2302; tdlib_only_count=158
- tdlib_vs_tdesktop: changed_count=0; overlap_count=2448; tdesktop_only=null; tdlib_only=accessPointRule, ephemeral.editMessage, help.configSimple, inputPeerPhotoFileLocationLegacy, inputStickerSetThumbLegacy, invokeWithApnsSecretPrefix, invokeWithBusinessConnectionPrefix, invokeWithGooglePlayIntegrityPrefix, invokeWithReCaptchaPrefix, ipPort, ipPortSecret, updateEphemeralBotCallbackQuery
miniprotoFast paths where they count. Explicit boundaries everywhere else.