You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So my bot answers inline queries with a button that is configured to open an app. However, the user data is not passed in it, unlike when opening the app through an inline keyboard button. And I was just wondering: what is the reasoning behind it?
As a workaround, I'm forced to create 'tokens' and store them in database, which get fed to the app url of the inline request button to identify the user. Is there another way?
This discussion was converted from issue #773 on September 15, 2025 08:39.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
So my bot answers inline queries with a button that is configured to open an app. However, the user data is not passed in it, unlike when opening the app through an inline keyboard button. And I was just wondering: what is the reasoning behind it?
As a workaround, I'm forced to create 'tokens' and store them in database, which get fed to the app url of the inline request button to identify the user. Is there another way?
Beta Was this translation helpful? Give feedback.
All reactions