stories.updateAlbum

Rename a story albums », or add, delete or reorder stories in it.

API section: Working with stories

stories.updateAlbum#5e5259b6 flags:# peer:InputPeer album_id:int title:flags.0?string delete_stories:flags.1?Vector<int> add_stories:flags.2?Vector<int> order:flags.3?Vector<int> = StoryAlbum;

Parameters

NameTypeDescription
flags # Bit mask: a field written flags.N?T is present only when bit N is set.
peer InputPeer The user or chat the request is about.
album_id int
title flags.0?string Title.
delete_stories flags.1?Vector<int>
add_stories flags.2?Vector<int>
order flags.3?Vector<int> Order of items — identifiers in the sequence you want.

Result

StoryAlbum

Possible errors

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

CodeTypeWhat it means
403 ALBUM_FORBIDDEN No access to this album.
400 ALBUM_ID_INVALID No album with this identifier exists.

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