telegram api method · layer 229 · #2c63a72b

stories.editStory

usable by users and bots

Edit an uploaded story

definition

stories.editStory#2c63a72b flags:# peer:InputPeer id:int media:flags.0?InputMedia media_areas:flags.3?Vector<MediaArea> caption:flags.1?string entities:flags.1?Vector<MessageEntity> privacy_rules:flags.2?Vector<InputPrivacyRule> music:flags.4?InputDocument = Updates;

parameters

nametypedescription
flags#Flags, see TL conditional fields
peerInputPeerPeer where the story was posted.
idintID of story to edit.
mediaflags.0?InputMediaIf specified, replaces the story media.
media_areasflags.3?Vector<MediaArea>Media areas associated to the story, see here » for more info.
captionflags.1?stringIf specified, replaces the story caption.
entitiesflags.1?Vector<MessageEntity>Message entities for styled text in the caption, if allowed by the stories_entities client configuration parameter ».
privacy_rulesflags.2?Vector<InputPrivacyRule>If specified, alters the privacy settings » of the story, changing who can or can't view the story.
musicflags.4?InputDocument

returns

Updates

errors (4)

codeerrordescription
400BUSINESS_CONNECTION_NOT_ALLOWEDThis method was invoked over a business connection using invokeWithBusinessConnection, but either (1) we're a user, and users cannot invoke methods over a business connection; (2) we're a bot, but business mode was disabled in @botfather or (3); we're a bot, but this method cannot be invoked over a business connection.
400PEER_ID_INVALIDThe provided peer id is invalid.
400STORY_NOT_MODIFIEDThe new story information you passed is equal to the previous story information, thus it wasn't modified.
401AUTH_KEY_UNREGISTEREDThe specified authorization key is not registered in the system (for example, a PFS temporary key has expired).

history

present in layers 160–229 · constructor id changed 3×

idlayers
#2aae7a41160
#a9b91ae4161–163
#b583ba46164–223
#2c63a72b224–229