edit_business_story()#
- Client.edit_business_story()#
Edits a story previously posted by the bot on behalf of a managed business account. Requires the can_manage_stories business bot right.
Usable by Users Bots- Parameters:
business_connection_id (
str
) – Unique identifier of the business connection.story_id (
int
) – Unique identifier of the story to edit.content (
InputStoryContent
, optional) – Content of the story.caption (
str
, optional) – Caption of the story, 0-2048 characters after entities parsing.parse_mode (
ParseMode
, optional) – By default, texts are parsed using both Markdown and HTML styles. You can combine both syntaxes together.caption_entities (List of
MessageEntity
) – List of special entities that appear in the caption, which can be specified instead of parse_mode.areas (List of
StoryArea
, optional) – List of of clickable areas to be shown on the story.privacy_settings (
StoryPrivacySettings
, optional) – The privacy settings for the story; ignored for stories sent to supergroup and channel chats. Defaults toStoryPrivacySettingsEveryone
.progress (
Callable
, optional) – Pass a callback function to view the file transmission progress. The function must take (current, total) as positional arguments (look at Other Parameters below for a detailed description) and will be called back each time a new file chunk has been successfully transmitted.progress_args (
tuple
, optional) – Extra custom arguments for the progress callback function. You can pass anything you need to be available in the progress callback scope; for example, a Message object or a Client instance in order to edit the message with the updated progress status.
- Returns:
Story
a story is returned.- Raises:
ValueError – In case of invalid arguments.
RPCError – In case of Telegram RPCError.