BOT_ACCESS_FORBIDDEN
BOT_ACCESS_FORBIDDEN
Section titled “BOT_ACCESS_FORBIDDEN”The specified method can be used over a business connection for some operations, but the specified query attempted an operation that is not allowed over a business connection.
Error details
Section titled “Error details”- code: 403
- parameterized: no
- mapped methods:
account.setGlobalPrivacySettings,messages.deleteMessages,payments.getPaymentForm,payments.getStarsStatus,payments.sendStarsForm,stories.deleteStories,stories.sendStory
Python error class
Section titled “Python error class”from miniproto.errors import BotAccessForbiddenPublic access: miniproto.errors.BotAccessForbidden.
Provenance
Section titled “Provenance”- structural source:
tdlib - RPC error source: https://core.telegram.org/api/errors
- prose merge precedence: TDLib → Telegram Desktop → Core JSON
- source note: Canonical structure is the pinned TDLib telegram_api.tl; Layer 229 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=78; core_only_count=18; overlap_count=2285; tdlib_only_count=195
- tdlib_vs_tdesktop: changed_count=0; overlap_count=2470; tdesktop_only=null; tdlib_only=accessPointRule, help.configSimple, inputPeerPhotoFileLocationLegacy, inputStickerSetThumbLegacy, invokeWithApnsSecretPrefix, invokeWithBusinessConnectionPrefix, invokeWithGooglePlayIntegrityPrefix, invokeWithReCaptchaPrefix, ipPort, ipPortSecret