diff --git a/data/web/corefork.telegram.org/api/stickers.html b/data/web/corefork.telegram.org/api/stickers.html index 2fc9000124..f69da39447 100644 --- a/data/web/corefork.telegram.org/api/stickers.html +++ b/data/web/corefork.telegram.org/api/stickers.html @@ -64,6 +64,20 @@ document#8fd4c4d8 flags:# id:long…">
Stickers can be contained in document constructors attached to messages, and always have an attribute of type documentAttributeSticker.
The documentAttributeSticker attribute contains information about the associated stickerset, the emoji that represents the sticker, and more.
There are multiple available sticker types:
+ +Like all files, stickers have a set of previews that should be handled as described in the file docs ».
+Stickers are organized in stickersets, and are also used in the following contexts:
+Static stickers are WebP images with the following specs:
They're identified by mime_type
field of the associated document, always equal to video/webm
.
See here » for tips on how to create the perfect video sticker, and here » for info on how to upload it using the API.
-Like all files, stickers have a set of previews that should be handled as described in the file docs ».
-inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;
-inputStickeredMediaDocument#438865b id:InputDocument = InputStickeredMedia;
-inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;
-
----functions---
-
-messages.getMaskStickers#640f82b8 hash:long = messages.AllStickers;
-messages.getAttachedStickers#cc5b67cc media:InputStickeredMedia = Vector<StickerSetCovered>;
inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;