Skip to content
miniproto logominiproto

TOPIC_ID_INVALID

TOPIC_ID_INVALID

Section titled “TOPIC_ID_INVALID”

The specified topic ID is invalid.

Error details

Section titled “Error details”
  • code: 400
  • parameterized: no
  • mapped methods: channels.deleteTopicHistory (not in selected Layer 229 schema), channels.editForumTopic (not in selected Layer 229 schema), channels.updatePinnedForumTopic (not in selected Layer 229 schema), messages.getDiscussionMessage, messages.getReplies

Python error class

Section titled “Python error class”
from miniproto.errors import TopicIdInvalid

Public access: miniproto.errors.TopicIdInvalid.

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
miniproto