url if specified, the client should open the URL, without showing a confirmation prompt. native_ui whether to open game URLs in a WebView or in native UI.premium_invoice_slug app config parameter »premium_invoice_slug app config parameter »Allow TCP WebRTC connections.
http://t.me/path?queryhttps://t.me/path?queryWhere t.me can also be telegram.me or telegram.dog.
Where t.me can also be telegram.me, telegram.dog, and the domain specified in the me_url_prefix field of the global configuration, obtainable using help.getConfig.
tg: link syntax examples:
tg:path?queryThe #fragment part is always ignored when parsing links.
Used to link to public users, groups and channels, see here for more info on how to handle them ».
-t.me syntax:
+t.me syntax:
t.me/<username>tg: syntax:
+tg: syntax:
tg://resolve?domain=<username>Parameters:
Used to link to specific messages in public or private groups and channels.
-t.me syntax (public links):
+t.me syntax (public links):
t.me/<username>/<id>?single&thread=<thread_id>&comment=<message_id>&t=<media_timestamp>t.me syntax (private links):
+t.me syntax (private links):
t.me/c/<channel>/<id>?single&thread=<thread_id>&comment=<message_id>&t=<media_timestamp>tg: syntax (public links):
+tg: syntax (public links):
tg://resolve?domain=<username>&post=<id>&single&thread=<thread>&comment=<comment>&t=<media_timestamp>tg: syntax (private links):
+tg: syntax (private links):
tg://privatepost?channel=<channelid>&post=<id>&single&thread=<thread>&comment=<comment>&t=<media_timestamp>Parameters:
Used for fill wallpapers » with a solid fill ».
-t.me syntax:
+t.me syntax:
t.me/bg/<hex_color>tg: syntax:
+tg: syntax:
tg://bg?color=<hex_color>Parameters:
Used for fill wallpapers » with a gradient fill ».
-t.me syntax:
+t.me syntax:
t.me/bg/<top_color>-<bottom_color>?rotation=<rotation>tg: syntax:
+tg: syntax:
tg://bg?gradient=<top_color>-<bottom_color>&rotation=<rotation>Parameters:
Used for fill wallpapers » with a freeform gradient fill ».
-t.me syntax:
+t.me syntax:
t.me/bg/<hex_color1>~<hex_color2>~<hex_color3>
t.me/bg/<hex_color1>~<hex_color2>~<hex_color3>~<hex_color4>tg: syntax:
+tg: syntax:
tg://bg?gradient=<hex_color1>~<hex_color2>~<hex_color3>
tg://bg?gradient=<hex_color1>~<hex_color2>~<hex_color3>~<hex_color4>Parameters:
@@ -376,9 +376,9 @@ tg://bg?gradient=<hex_color1>~<hex_color2>~<hex_color3>~<heUsed for pattern wallpapers » with a solid fill ».
-t.me syntax:
+t.me syntax:
t.me/bg/<slug>?intensity=<intensity>&bg_color=<bg_color>&mode=<mode>tg: syntax:
+tg: syntax:
tg://bg?slug=<slug>&intensity=<intensity>&bg_color=<bg_color>&mode=<mode>Parameters:
Used for pattern wallpapers » with a gradient fill ».
-t.me syntax:
+t.me syntax:
t.me/bg/<slug>?intensity=<intensity>&bg_color=<top_color>-<bottom_color>&rotation=<rotation>&mode=<mode>tg: syntax:
+tg: syntax:
tg://bg?slug=<slug>&intensity=<intensity>&bg_color=<top_color>-<bottom_color>&rotation=<rotation>&mode=<mode>Parameters:
Used for pattern wallpapers » with a freeform gradient fill ».
-t.me syntax:
+t.me syntax:
t.me/bg/<slug>?intensity=<intensity>&bg_color=<hex_color1>~<hex_color2>~<hex_color3>&mode=<mode>
t.me/bg/<slug>?intensity=<intensity>&bg_color=<hex_color1>~<hex_color2>~<hex_color3>~<hex_color4>&mode=<mode>tg: syntax:
+tg: syntax:
tg://bg?slug=<slug>&intensity=<intensity>&bg_color=<hex_color1>~<hex_color2>~<hex_color3>&mode=<mode>
tg://bg?slug=<slug>&intensity=<intensity>&bg_color=<hex_color1>~<hex_color2>~<hex_color3>~<hex_color4>&mode=<mode>Parameters:
@@ -517,9 +517,9 @@ tg://bg?slug=<slug>&intensity=<intensity>&bg_color=<hex_cUsed to link to bots.
-t.me syntax:
+t.me syntax:
t.me/<bot_username>?start=<parameter>tg: syntax:
+tg: syntax:
tg://resolve?domain=<bot_username>&start=<parameter>Parameters:
t.me syntax:
+t.me syntax:
t.me/invoice/<slug>
t.me/$<slug>tg: syntax:
+tg: syntax:
tg://invoice?slug=<slug>Parameters:
Used to import custom language packs using langpack.getLangPack.
-t.me syntax:
+t.me syntax:
t.me/setlanguage/<slug>tg: syntax:
+tg: syntax:
tg://setlanguage?lang=<slug>Parameters:
t.me syntax:
+t.me syntax:
t.me/passport?bot_id=<bot_user_id>&scope=<scope>&public_key=<public_key>&nonce=<nonce>tg: syntax:
+tg: syntax:
tg://resolve?domain=telegrampassport&bot_id=<bot_user_id>&scope=<scope>&public_key=<public_key>&nonce=<nonce>Different from login code links.
These links are used to confirm ownership of the phone number, to prevent account deletion: see the account deletion docs for more info on how to handle them ».
t.me syntax:
+t.me syntax:
t.me/confirmphone?phone=<phone>&hash=<hash>tg: syntax:
+tg: syntax:
tg://confirmphone?phone=<phone>&hash=<hash>Parameters:
Used by official apps to show the Telegram Premium subscription page.
-tg: syntax:
+tg: syntax:
tg://premium_offer?ref=<referrer>Parameters:
Used for socks5 proxies.
-t.me syntax:
+t.me syntax:
t.me/socks?server=<server>&port=<port>&user=<user>&pass=<pass>tg: syntax:
+tg: syntax:
tg://socks?server=<server>&port=<port>&user=<user>&pass=<pass>Parameters:
Used by QR code login.
-tg: syntax:
+tg: syntax:
tg://login?token=<base64encodedtoken>Parameters:
Used to import stickersets:
-t.me syntax:
+t.me syntax:
t.me/addstickers/<name>tg: syntax:
+tg: syntax:
tg://addstickers?set=<name>Parameters:
Used to import custom emoji stickersets:
-t.me syntax:
+t.me syntax:
t.me/addemoji/<name>tg: syntax:
+tg: syntax:
tg://addemoji?set=<name>Parameters:
t.me syntax:
+t.me syntax:
t.me/addtheme/<name>tg: syntax:
+tg: syntax:
tg://addtheme?slug=<name>Parameters:
t.me syntax:
+t.me syntax:
t.me/<username>?attach=<bot_username>
t.me/<username>?attach=<bot_username>&startattach=<start_parameter>
t.me/<bot_username>?startattach&choose=users+bots+groups+channels
t.me/<bot_username>?startattach=<start_parameter>&choose=users+bots+groups+channels
t.me/+<phone_number>?attach=<bot_username>
t.me/+<phone_number>?attach=<bot_username>&startattach=<start_parameter>tg: synax:
+tg: syntax:
tg://resolve?domain=<username>&attach=<bot_username>
tg://resolve?domain=<username>&attach=<bot_username>&startattach=<start_parameter>
tg://resolve?domain=<bot_username>&startattach&choose=users+bots+groups+channels
@@ -989,7 +989,7 @@ tg://resolve?domain=<bot_username>&startattach=<start_parameter>
tg://resolve?phone=<phone_number>&attach=<bot_username>
tg://resolve?phone=<phone_number>&attach=<bot_username>&startattach=<start_parameter>If a client encounters a tg: link type not listed on this page, help.getDeepLinkInfo should be invoked with just the path component of the link.
If a client encounters a tg: link type not listed on this page, help.getDeepLinkInfo should be invoked with just the path component of the link.
Schema:
help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
diff --git a/data/web/corefork.telegram.org/constructor/config.html b/data/web/corefork.telegram.org/constructor/config.html
index e2c116ff58..a1620e3179 100644
--- a/data/web/corefork.telegram.org/constructor/config.html
+++ b/data/web/corefork.telegram.org/constructor/config.html
@@ -274,7 +274,7 @@
me_url_prefix
string
-The domain to use to parse in-app links.
For example t.me indicates that t.me/username links should parsed to @username, t.me/addsticker/name should be parsed to the appropriate stickerset and so on...
+The domain to use to parse deep links ».
autoupdate_url_prefix
@@ -353,6 +353,8 @@
Top peer rating
If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).
Telegram Passport Manual
+Deep links
+Telegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.
Uploading and Downloading Files
How to transfer large data batches correctly.
diff --git a/data/web/corefork.telegram.org/constructor/inputInvoiceSlug.html b/data/web/corefork.telegram.org/constructor/inputInvoiceSlug.html
index 54d4b21f2f..a603df9b62 100644
--- a/data/web/corefork.telegram.org/constructor/inputInvoiceSlug.html
+++ b/data/web/corefork.telegram.org/constructor/inputInvoiceSlug.html
@@ -4,10 +4,10 @@
inputInvoiceSlug
-
+
-
+
@@ -42,7 +42,7 @@
inputInvoiceSlug
- An invoice slug taken from a t.me/invoice/ link or from the premium_invoice_slug app config parameter »
+ An invoice slug taken from an invoice deep link or from the premium_invoice_slug app config parameter »
-
@@ -76,6 +76,8 @@
Type
Related pages
+Deep links
+Telegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.
Client configuration
The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.
diff --git a/data/web/corefork.telegram.org/constructor/inputStickerSetShortName.html b/data/web/corefork.telegram.org/constructor/inputStickerSetShortName.html
index 56d6bb5bcf..476c35a733 100644
--- a/data/web/corefork.telegram.org/constructor/inputStickerSetShortName.html
+++ b/data/web/corefork.telegram.org/constructor/inputStickerSetShortName.html
@@ -4,10 +4,10 @@
inputStickerSetShortName
-
+
-
+
@@ -42,7 +42,7 @@
inputStickerSetShortName
- Stickerset by short name, from tg://addstickers?set=short_name
+ Stickerset by short name, from a stickerset deep link »
-
@@ -69,12 +69,15 @@
short_name
string
-From tg://addstickers?set=short_name
+Short name from a stickerset deep link »
Telegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.
diff --git a/data/web/corefork.telegram.org/constructor/messageActionPaymentSent.html b/data/web/corefork.telegram.org/constructor/messageActionPaymentSent.html index aee697859c..7c65468506 100644 --- a/data/web/corefork.telegram.org/constructor/messageActionPaymentSent.html +++ b/data/web/corefork.telegram.org/constructor/messageActionPaymentSent.html @@ -94,7 +94,7 @@premium_invoice_slug app config parameter »premium_invoice_slug app config parameter »Telegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.
The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.
diff --git a/data/web/corefork.telegram.org/constructor/premiumGiftOption.html b/data/web/corefork.telegram.org/constructor/premiumGiftOption.html index c2aa7eaf3a..237fbe88b7 100644 --- a/data/web/corefork.telegram.org/constructor/premiumGiftOption.html +++ b/data/web/corefork.telegram.org/constructor/premiumGiftOption.html @@ -89,7 +89,7 @@Telegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.
diff --git a/data/web/corefork.telegram.org/method/auth.exportLoginToken b/data/web/corefork.telegram.org/method/auth.exportLoginToken index df3670c07f..4199a5a356 100644 --- a/data/web/corefork.telegram.org/method/auth.exportLoginToken +++ b/data/web/corefork.telegram.org/method/auth.exportLoginToken @@ -4,10 +4,10 @@Generate a login token, for login via QR code.
-The generated login token should be encoded using base64url, then shown as a tg://login?token=base64encodedtoken URL in the QR code.
tg://login?token=base64encodedtoken deep link » in the QR code.
For more info, see login via QR code.
QR code login flow
QR code login flow
+Telegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.
t.me/joinchat/hash or t.me/+hashTelegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.
diff --git a/data/web/corefork.telegram.org/method/messages.importChatInvite b/data/web/corefork.telegram.org/method/messages.importChatInvite index 3477aced89..a953e614a3 100644 --- a/data/web/corefork.telegram.org/method/messages.importChatInvite +++ b/data/web/corefork.telegram.org/method/messages.importChatInvite @@ -77,7 +77,7 @@hash from t.me/joinchat/hashhash from a chat invite deep linkTelegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.
diff --git a/data/web/corefork.telegram.org/method/messages.requestWebView b/data/web/corefork.telegram.org/method/messages.requestWebView index ed96531616..e9678f1f3b 100644 --- a/data/web/corefork.telegram.org/method/messages.requestWebView +++ b/data/web/corefork.telegram.org/method/messages.requestWebView @@ -102,7 +102,7 @@https://t.me/username?attach=botusername&startattach=data or https://t.me/botusername?startattach=data link, start_param should contain the data from the startattach parameter.start_param should contain the data from the startattach parameter.Terminate webview interaction started with messages.requestWebView, sending the specified message to the chat on behalf of the user.
Telegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.
Indicate to the server (from the user side) that the user is still using a web app.
diff --git a/data/web/corefork.telegram.org/methods.html b/data/web/corefork.telegram.org/methods.html index 78ad5a479d..6c9be6421b 100644 --- a/data/web/corefork.telegram.org/methods.html +++ b/data/web/corefork.telegram.org/methods.html @@ -158,7 +158,7 @@tg://login?token=base64encodedtoken URL in the QR code.tg://login?token=base64encodedtoken deep link » in the QR code.premium_invoice_slug app config parameter »premium_invoice_slug app config parameter »Contains information about a tg:// deep link
+Contains information about an unsupported deep link »
t.me linkTelegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.