stickers.createStickerSet

Create a stickerset.

API section: Working with stickers »

stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true emojis:flags.5?true text_color:flags.6?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;

Parameters

NameTypeDescription
flags # Bit mask: a field written flags.N?T is present only when bit N is set.
masks flags.0?true
emojis flags.5?true
text_color flags.6?true
user_id InputUser User identifier.
title string Title.
short_name string Short name of the set — the part that appears in its link.
thumb flags.2?InputDocument Reduced copy used for preview.
stickers Vector<InputStickerSetItem> List of stickers.
software flags.3?string

Result

messages.StickerSet

Possible errors

Read out of the handler itself — this is what the server actually returns for this method.

CodeTypeWhat it means
400 SHORT_NAME_INVALID The short name fails validation.
400 SHORT_NAME_OCCUPIED The short name is already taken.

Common to every call

CodeTypeWhat it means
401 AUTH_KEY_UNREGISTERED The server does not know this session: the key was revoked, expired, or the call was made before authorisation.
401 API_ID_INVALID This api_id was never issued or has been blocked. Keys come from my.ansible.su.
400 CONNECTION_LAYER_INVALID The client did not declare a layer, or declared one the server does not know.
420 FLOOD_WAIT_X Too often. Do not retry for X seconds — the number arrives in the error text.
500 INTERNAL A failure on our side. The request may be retried; if it keeps failing, it is a bug of ours.

Related pages

Types used here