answerInlineQuery | R Documentation |
Use this method to send answers to an inline query. No more than 50 results per query are allowed.
answerInlineQuery( inline_query_id, results, cache_time = 300L, is_personal = NULL, next_offset = NULL, switch_pm_text = NULL, switch_pm_parameter = NULL )
inline_query_id |
Unique identifier for the answered query. |
results |
A list of |
cache_time |
(Optional). The maximum amount of time in seconds that the result of the inline query may be cached on the server. |
is_personal |
(Optional). Pass |
next_offset |
(Optional). Pass the offset that a client should send in the next query with the same text to receive more results. Pass an empty string if there are no more results or if you don't support pagination. Offset length can't exceed 64 bytes. |
switch_pm_text |
(Optional). If passed, clients will display a button
with specified text that switches the user to a private chat with the
bot and sends the bot a start message with the parameter
|
switch_pm_parameter |
(Optional). Deep-linking parameter for the
Example: An inline bot that sends YouTube videos can ask the user to connect the bot to their YouTube account to adapt search results accordingly. To do this, it displays a 'Connect your YouTube account' button above the results, or even before showing any. The user presses the button, switches to a private chat with the bot and, in doing so, passes a start parameter that instructs the bot to return an auth link. Once done, the bot can offer a switch_inline button so that the user can easily return to the chat where they wanted to use the bot's inline capabilities. |
To enable this option, send the /setinline
command to
@BotFather and provide the placeholder text
that the user will see in the input field after typing your bot's name.
You can also use it's snake_case equivalent answer_inline_query
.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.