Tier 4: niche Bot API methods — defer to callApi escape hatch, implement on request

[windkh]

Tier 4 — Niche methods: defer to the callApi escape hatch / implement on request

From the V18 coverage analysis (#453). Specialized audiences and low Node-RED demand. Recommendation: do not hand-wire these; once the callApi raw-API escape hatch lands they are all reachable with correct signatures. Add first-class types only if users ask.

Feature area	Bot API	Methods
Sticker set management	≤3.0–7.2	createNewStickerSet, addStickerToSet, uploadStickerFile, deleteStickerFromSet, setStickerPositionInSet, getStickerSet, getCustomEmojiStickers, deleteStickerSet, setStickerEmojiList, setStickerKeywords, setStickerMaskPosition, setStickerSetTitle, setStickerSetThumbnail, setCustomEmojiStickerSetThumbnail, replaceStickerInSet
Paid media	7.6	sendPaidMedia
Gifts	8.0–9.3	getAvailableGifts, sendGift, giftPremiumSubscription, convertGiftToStars, transferGift, upgradeGift, getBusinessAccountGifts, getUserGifts, getChatGifts
Stories	9.0	postStory, editStory, deleteStory, repostStory
Business accounts	9.0	getBusinessConnection, readBusinessMessage, deleteBusinessMessages, setBusinessAccountName/Bio/Username/ProfilePhoto, removeBusinessAccountProfilePhoto, setBusinessAccountGiftSettings, getBusinessAccountStarBalance, transferBusinessAccountStars
Verification	8.2	verifyUser, verifyChat, removeUserVerification, removeChatVerification
Suggested posts	9.2	approveSuggestedPost, declineSuggestedPost
Games	≤3.0	sendGame, setGameScore, getGameHighScores
Passport	4.0	setPassportDataErrors
Misc / very new (9.3–10.1)	9.3–10.1	sendMessageDraft, getUserProfileAudios, setChatMemberTag, getManagedBotToken, replaceManagedBotToken, answerGuestQuery, sendLivePhoto, getUserPersonalChatMessages, sendRichMessage, sendRichMessageDraft, answerChatJoinRequestQuery, sendChatJoinRequestWebApp, savePreparedInlineMessage, setUserEmojiStatus, editUserStarSubscription, getUserChatBoosts, unpinAllGeneralForumTopicMessages

Related: #453, #448.

[windkh]

On hold pending #501 — do not implement this against the v1 API surface.

node-telegram-bot-api@2.0.0 is released and describes itself as "a from-scratch redesign with no backward compatibility" with the v1 TelegramBot surface. Among other things it replaces positional arguments with params objects under a uniform bot.api.* namespace, and covers Bot API 10.2 natively.

This issue was written on 2026-06-17 against v1. Two things about it are now uncertain:

• Whether the work is still needed. Methods listed here may already be reachable through v2's bot.api.* surface, in which case the remaining work is exposing them in the nodes, not implementing them.
• Whether the tiering still holds. v2 changes the effort profile, so the split across Tier 1–4 may need re-cutting rather than the tiers being worked in order.

Anything implemented against v1 in the meantime would very likely be thrown away in the port.

Action: this issue is re-checked as part of #501, after the breaking-change analysis it requires. It stays open until then — no assumption either way. Kept as-is on purpose: it records what users asked for, and that need survives the library change even if the implementation does not.