set_http_callback
From SmartBots Developers Docs
Revision as of 11:31, 22 February 2022 by Gg (Talk | contribs) (Created page with "{{DISPLAYTITLE: set_http_callback}} <onlyinclude>Set HTTP callback to be called on group events.</onlyinclude> {{API Variables Table}} {{API HTTP Group Required Vars|invite}...")
Set HTTP callback to be called on group events.
Variables
The following table shows input values (you send them with the API call) and returned output values.
| Variable | Required | Description | |
|---|---|---|---|
| Input base: | |||
| action | yes | = invite | |
| apikey | yes | Your personal developer's API key. | |
| secret | yes | Security code of the group you are using. | |
| secret_sha1 | optional | The same as "secret" but hashed using SHA1 (useful if you don't want to keep plain customer's passwords) | |
| Input: | |||
| apikey | yes | Developer's API key of the callback URL owner (see comments below) | |
| yes | the customer's email at SmartBots | ||
| group | yes | the group name (must be listed with SmartBots!) | |
| secret_sha1 | yes | The SHA1 hash of the Group Security Code | |
| app_name | yes | The application name (provided by developer, visible to the user) | |
| app_uuid | yes | The application UUID (provided by developer, not visible) | |
| url | yes | The URL to be called on group events | |
| Output (JSON formatted): | |||
| OK | command completed successfully | ||
| anything else | Request failed, the fail reason is returned | ||
Comments
This API call required information both from developer of an application (which received the callback) and from a customer.
The developer should provide the following data:
- apikey - see SmartBots docs
<< return back to group commands
