diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index dee8c5cf4d..a1ecdeeff7 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -49,22 +49,39 @@

To view all the changes since the last update, start reading the changelog @ Layer 159.

Most importantly, the following detailed articles were added:

Also added documentation for streamed uploads and improved the method queue documentation.

The following new deep links were added:

And now, here are the changes that were made in this layer.

Introducing Telegram Stories, channel boosts, session confirmation, side menu Mini Apps, direct link Mini Apps, custom methods and multiple new events for Mini Apps and a close friends list.

+

A new story premium feature identifier was added.

+

The following new web events were also added to provide more functionality to mini apps:

+ +

Also, the following changes were made to existing web events:

+

Schema changes

New Methods

Once a story is successfully uploaded, an updateStoryID will be returned, indicating the story ID (id) that was attributed to the story (like for messages, random_id indicates the random_id that was passed to stories.sendStory: this way, you can tell which story was assigned a specific id by checking which stories.sendStory call has the returned random_id).

Also, posting a story will emit an updateStory both for us, and for our subscribers/contacts (even if they have hidden our stories).

@@ -200,7 +201,7 @@ When the stories of a user are marked as hidden, the stories_hidden stories.getStoryViewsList#7ed23c57 flags:# just_contacts:flags.0?true reactions_first:flags.2?true peer:InputPeer q:flags.1?string id:int offset:string limit:int = stories.StoryViewsList; stories.getStoriesViews#28e16cc8 peer:InputPeer id:Vector<int> = stories.StoryViews; -

Use stories.getStoryViewsList to obtain the full list of users that have viewed a specific story we posted, returned as a list of storyView constructors; pass the returned next_offset (if present) to offset to paginate through the results.

+

Use stories.getStoryViewsList to obtain the full list of users that have viewed a specific story we posted, returned as a list of storyView constructors; pass the returned next_offset (if present) to offset to paginate through the results; the full list is available at all times only to Premium users, and will be hidden to non-Premium users story_viewers_expire_period » seconds after the story expires.

Use stories.getStoriesViews to obtain info about the view count, forward count, reactions and recent viewers list of one or more stories, using a single, unpaginated method call, obviously potentially returning less info than stories.getStoryViewsList.

Replying to stories

inputReplyToStory#15b0f283 user_id:InputUser story_id:int = InputReplyTo;
diff --git a/data/web/corefork.telegram.org/method/account.finishTakeoutSession.html b/data/web/corefork.telegram.org/method/account.finishTakeoutSession.html
index 0aae3ee380..043c755062 100644
--- a/data/web/corefork.telegram.org/method/account.finishTakeoutSession.html
+++ b/data/web/corefork.telegram.org/method/account.finishTakeoutSession.html
@@ -4,10 +4,10 @@
     
     account.finishTakeoutSession
     
-    
+    
     
     
-    
+    
     
 
 
@@ -42,7 +42,7 @@
   
   

account.finishTakeoutSession

-

Finish account takeout session

+

Terminate a takeout session, see here » for more info.

+ +

Related pages

+

Takeout API

+

Telegram's API allows users to export all of their information through the takeout API.

diff --git a/data/web/corefork.telegram.org/method/account.initTakeoutSession.html b/data/web/corefork.telegram.org/method/account.initTakeoutSession.html index 3f24dfae71..544d27fb5c 100644 --- a/data/web/corefork.telegram.org/method/account.initTakeoutSession.html +++ b/data/web/corefork.telegram.org/method/account.initTakeoutSession.html @@ -4,10 +4,10 @@ account.initTakeoutSession - + - + @@ -42,7 +42,7 @@

account.initTakeoutSession

-

Initialize account takeout session

+

Initialize a takeout session, see here » for more info.

+

How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.

+

Takeout API

+

Telegram's API allows users to export all of their information through the takeout API.

diff --git a/data/web/corefork.telegram.org/method/bots.invokeWebViewCustomMethod.html b/data/web/corefork.telegram.org/method/bots.invokeWebViewCustomMethod.html index 94e7ebd058..29132c8b0a 100644 --- a/data/web/corefork.telegram.org/method/bots.invokeWebViewCustomMethod.html +++ b/data/web/corefork.telegram.org/method/bots.invokeWebViewCustomMethod.html @@ -4,10 +4,10 @@ bots.invokeWebViewCustomMethod - + - + @@ -42,7 +42,8 @@

bots.invokeWebViewCustomMethod

-

Send a custom request from a mini bot app

+

Send a custom request from a mini bot app, triggered by a web_app_invoke_custom_method event ».

+

The response should be sent using a custom_method_invoked event, see here » for more info on the flow.

+

Bots can offer users interactive HTML5 web apps to completely replace any website.

+

Web events

+

How telegram apps interact with webpages

diff --git a/data/web/corefork.telegram.org/method/channels.getLeftChannels.html b/data/web/corefork.telegram.org/method/channels.getLeftChannels.html index d98ea47ee8..c90dc142d7 100644 --- a/data/web/corefork.telegram.org/method/channels.getLeftChannels.html +++ b/data/web/corefork.telegram.org/method/channels.getLeftChannels.html @@ -4,10 +4,10 @@ channels.getLeftChannels - + - + @@ -42,7 +42,7 @@

channels.getLeftChannels

-

Get a list of channels/supergroups we left

+

Get a list of channels/supergroups we left, requires a takeout session, see here » for more info.

+

How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.

+

Takeout API

+

Telegram's API allows users to export all of their information through the takeout API.

diff --git a/data/web/corefork.telegram.org/method/contacts.getSaved.html b/data/web/corefork.telegram.org/method/contacts.getSaved.html index 0066b3e0f7..b325b55dce 100644 --- a/data/web/corefork.telegram.org/method/contacts.getSaved.html +++ b/data/web/corefork.telegram.org/method/contacts.getSaved.html @@ -4,10 +4,10 @@ contacts.getSaved - + - + @@ -42,7 +42,7 @@

contacts.getSaved

-

Get all contacts

+

Get all contacts, requires a takeout session, see here » for more info.

+ +

Related pages

+

Takeout API

+

Telegram's API allows users to export all of their information through the takeout API.

diff --git a/data/web/corefork.telegram.org/method/invokeWithTakeout.html b/data/web/corefork.telegram.org/method/invokeWithTakeout.html index 652acaefba..3477b47361 100644 --- a/data/web/corefork.telegram.org/method/invokeWithTakeout.html +++ b/data/web/corefork.telegram.org/method/invokeWithTakeout.html @@ -4,10 +4,10 @@ invokeWithTakeout - + - + @@ -42,7 +42,7 @@

invokeWithTakeout

-

Invoke a method within a takeout session

+

Invoke a method within a takeout session, see here » for more info.

+

Bots can use this method

+

Related pages

+

Takeout API

+

Telegram's API allows users to export all of their information through the takeout API.

diff --git a/data/web/corefork.telegram.org/method/stories.canSendStory.html b/data/web/corefork.telegram.org/method/stories.canSendStory.html index c56f838738..ef60a4df9d 100644 --- a/data/web/corefork.telegram.org/method/stories.canSendStory.html +++ b/data/web/corefork.telegram.org/method/stories.canSendStory.html @@ -111,7 +111,7 @@ 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. +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 diff --git a/data/web/corefork.telegram.org/method/stories.getPeerStories.html b/data/web/corefork.telegram.org/method/stories.getPeerStories.html index a55f79c4f2..c63a3f5aa5 100644 --- a/data/web/corefork.telegram.org/method/stories.getPeerStories.html +++ b/data/web/corefork.telegram.org/method/stories.getPeerStories.html @@ -89,6 +89,11 @@ 400 +CHANNEL_INVALID +The provided channel is invalid. + + +400 CHANNEL_PRIVATE You haven't joined this channel/supergroup. diff --git a/data/web/corefork.telegram.org/method/stories.sendStory.html b/data/web/corefork.telegram.org/method/stories.sendStory.html index 9c693e9c54..0f3d564601 100644 --- a/data/web/corefork.telegram.org/method/stories.sendStory.html +++ b/data/web/corefork.telegram.org/method/stories.sendStory.html @@ -181,7 +181,7 @@ 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. +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 diff --git a/data/web/corefork.telegram.org/method/upload.reuploadCdnFile.html b/data/web/corefork.telegram.org/method/upload.reuploadCdnFile.html index cf19e9e980..e73ba1c880 100644 --- a/data/web/corefork.telegram.org/method/upload.reuploadCdnFile.html +++ b/data/web/corefork.telegram.org/method/upload.reuploadCdnFile.html @@ -93,11 +93,6 @@ 400 -AES_DECRYPT_FAILED -  - - -400 CDN_METHOD_INVALID You can't call this method in a CDN DC.