Difference between revisions of "HTTP API/Bot Commands/reply dialog"
From SmartBots Developers Docs
(Created page with "<onlyinclude>Virtually "presses" a pop-up dialog button (which was displayed by an in-world script).</onlyinclude> {{API Variables Table}} {{API HTTP Required Vars|reply_dia...") |
(→Examples) |
||
| Line 17: | Line 17: | ||
== Examples == | == Examples == | ||
| − | {{ | + | {{HTTP API Example: reply to menu dialog}} |
{{HTTP API Bot - standard footer}} | {{HTTP API Bot - standard footer}} | ||
Revision as of 07:55, 29 June 2016
Virtually "presses" a pop-up dialog button (which was displayed by an in-world script).
Variables
The following table shows input values (you send them with the API call) and returned output values.
| Variable | Required | Description | ||
|---|---|---|---|---|
| This API command applies only for Standard bot | ||||
| Input basic parameters: | ||||
| action | yes | = reply_dialog | ||
| apikey | yes | Your personal developer's API key. | ||
| botname | yes | Your bot's SL login. | ||
| secret | yes | Bot access code of your bot. | ||
| dataType | optional | Set to "json" to get JSON reply instead of URL-encoded string | ||
| custom | optional | The custom data (string) to be passed back to caller script. This value will be returned back to the caller in HTTP response. | ||
| Input: | ||||
| channel | yes | the dialog channel (either positive or negative value) | ||
| object | yes | UUID of the object which sent us the dialog | ||
| button | yes | the text of the dialog button to press | ||
| Output: | ||||
| (to be received in http_response LSL event, see docs for details) | ||||
| result | OK - command completed successfully FAIL - command failed | |||
| resulttext | Detailed reason for the failure. | |||
| custom | The value from input "custom" parameter. See above. | |||
Examples
Template:HTTP API Example: reply to menu dialog
<< return back to Bot commands
(Miss an API call or parameter? Submit your request in forum)
