telegram api method · layer 229 · #30eb63f0

stories.canSendStory

usable by users

Check whether we can post stories as the specified peer.

definition

stories.canSendStory#30eb63f0 peer:InputPeer = stories.CanSendStoryCount;

name	type	description
`peer`	InputPeer	The peer from which we wish to post stories.

code	error	description
400	BOOSTS_REQUIRED	The specified channel must first be boosted by its users in order to perform this action.
400	BUSINESS_CONNECTION_NOT_ALLOWED	This 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.
400	CHANNEL_INVALID	The provided channel is invalid.
400	CHAT_ADMIN_REQUIRED	You must be an admin in this chat to do this.
400	PEER_ID_INVALID	The provided peer id is invalid.
400	PREMIUM_ACCOUNT_REQUIRED	A premium account is required to execute this action.
400	STORIES_TOO_MUCH	You have hit the maximum active stories limit as specified by the `story_expiring_limit_*` client configuration parameters: you should buy a Premium subscription, delete an active story, or wait for the oldest story to expire.
400	STORY_SEND_FLOOD_MONTHLY_%d	You've hit the monthly story limit as specified by the `stories_sent_monthly_limit_*` client configuration parameters: wait %d seconds before posting a new story.
400	STORY_SEND_FLOOD_WEEKLY_%d	You've hit the weekly story limit as specified by the `stories_sent_weekly_limit_*` client configuration parameters: wait for %d seconds before posting a new story.
401	AUTH_KEY_UNREGISTERED	The specified authorization key is not registered in the system (for example, a PFS temporary key has expired).

present in layers 162–229 · constructor id changed 2×