inputMediaGeoPoint
inputMediaGeoPoint
Section titled “inputMediaGeoPoint”No description provided by the pinned schema.
Signature
Section titled “Signature”inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;Result type
Section titled “Result type”InputMedia
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| geo_point | InputGeoPoint | — | — | No description provided by the pinned schema. |
Python binding
Section titled “Python binding”from miniproto.raw.types import InputMediaGeoPointPublic access: miniproto.raw.types.InputMediaGeoPoint.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.types import InputMediaGeoPoint
# Naming the raw constructor class is local only; it performs no I/O or network request.constructor_type = InputMediaGeoPointResult family
Section titled “Result family”Relationships
Section titled “Relationships”- Result family:
InputMedia - Related constructors:
inputMediaContact,inputMediaDice,inputMediaDocument,inputMediaDocumentExternal,inputMediaEmpty,inputMediaGame,inputMediaGeoLive,inputMediaInvoice,inputMediaPaidMedia,inputMediaPhoto,inputMediaPhotoExternal,inputMediaPoll,inputMediaStakeDice,inputMediaStory,inputMediaTodo,inputMediaUploadedDocument,inputMediaUploadedPhoto,inputMediaVenue,inputMediaWebPage - Accepted by:
bots.addPreviewMedia,bots.deletePreviewMedia,bots.editPreviewMedia,bots.reorderPreviewMedias,ephemeral.editMessage,ephemeral.sendMessage,messages.editInlineBotMessage,messages.editMessage,messages.saveDraft,messages.sendMedia,messages.uploadImportedMedia,messages.uploadMedia,payments.exportInvoice,stories.editStory,stories.sendStory,draftMessage,inputMediaInvoice,inputMediaPaidMedia,inputMediaPoll,inputPollAnswer,inputSingleMedia
Provenance
Section titled “Provenance”- 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 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