diff --git a/data/web/corefork.telegram.org/api/business.html b/data/web/corefork.telegram.org/api/business.html index 2a8a4bda8e..44ddbb2b8e 100644 --- a/data/web/corefork.telegram.org/api/business.html +++ b/data/web/corefork.telegram.org/api/business.html @@ -334,7 +334,7 @@ The created deep link is returned i

Use account.resolveBusinessChatLink to open a business chat link, obtaining the peer to contact and (if set) the message to pre-fill, also increasing the link's view counter.

The last three methods listed above take a business chat link slug, which should be extracted from a business chat link as specified here ».

All listed methods except account.resolveBusinessChatLink require a Telegram Business subscription (currently included in Telegram Premium subscriptions).

-

An account may create a maximum of business_chat_links_limit business chat links, prompt the user to delete older links if the limit is reached.

+

An account may create a maximum of business_chat_links_limit business chat links: attempts to exceed this limit will emit a CHATLINKS_TOO_MUCH RPC error, prompting the user to delete older links.

Connected bots

inputBusinessBotRecipients#c4e5921e flags:# existing_chats:flags.0?true new_chats:flags.1?true contacts:flags.2?true non_contacts:flags.3?true exclude_selected:flags.5?true users:flags.4?Vector<InputUser> exclude_users:flags.6?Vector<InputUser> = InputBusinessBotRecipients;
 
diff --git a/data/web/corefork.telegram.org/api/errors.html b/data/web/corefork.telegram.org/api/errors.html
index 2bcea9e997..23f80f39f9 100644
--- a/data/web/corefork.telegram.org/api/errors.html
+++ b/data/web/corefork.telegram.org/api/errors.html
@@ -49,7 +49,7 @@ An error is characterized by several parameters:

 
Error Type

 
A string literal in the form of /[A-Z_0-9]+/, which summarizes the problem. For example, AUTH_KEY_UNREGISTERED. This is an optional parameter.

 
Error Database

-
A full human-readable JSON list of RPC errors that can be returned by all methods in the API can be found here », what follows is a description of its fields:  

+
A full human-readable JSON list of RPC errors that can be returned by all methods in the API can be found here », what follows is a description of its fields: