Animated Emojis

Graphical telegram clients should transform emojis into their respective animated version.

inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;

messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;


messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;

On startup, clients should fetch the animated emoji stickerset by calling the messages.getStickerSet method, providing inputStickerSetAnimatedEmoji to the stickerset field.
The returned stickerset will contain a set of animated stickers, one for each of the supported emojis.

Clients should substitute messages containing only one instance of one of the allowed emojis with the respective animated sticker.

Animated emojis should loop only once when first sent or received, or when clicked.

For special dice emojis like ๐ŸŽฒ, ๐ŸŽฏ, or ๐Ÿ€, clients are supposed to behave differently both when sending and receiving such emojis: click here for more info ยป.

Emojis with sounds

Certained animated emojis should play sound when clicked, as specified by server-side configuration.

The returned JSON object will contain the following map, with a list of file IDs to download:

    "emojies_sounds": {
        "\ud83c\udf83": {
            "id": "4956223179606458539",
            "access_hash": "-2107001400913062971",
            "file_reference_base64": "AF-4ApC7ukC0UWEPZN0TeSJURe7T"
        "\u26b0": {
            "id": "4956223179606458540",
            "access_hash": "-1498869544183595185",
            "file_reference_base64": "AF-4ApCLKMGt96WCvLm58kbqZHd3"
        "\ud83e\udddf\u200d\u2642": {
            "id": "4960929110848176331",
            "access_hash": "3986395821757915468",
            "file_reference_base64": "AF-4ApAedNln3IMEHH-SUQuH8L9g"

The file reference field should be base64-decoded before downloading the file