Get the features that are enabled for the requesting bot
Changed onAllows bots to check which features an administrator has enabled for them, without requiring administrator credentials. The request is signed with the shared bot secret like all other bot requests: the signature is computed over the random seed and the conversation token sent in the request body, which is used to look the bot up. Keeping the token in the signed body binds the request to the conversation, so the signature headers on their own cannot be replayed. Required capability: bot-features-api
Request
- The document declares no server URL.
- Auth
- none
- or HTTP bearer
- or HTTP basic
Path parameters
Headers
Random seed (at least 32 bytes) used together with the conversation token to generate the SHA256-HMAC request signature
SHA256-HMAC signature over the concatenation of the random seed and the conversation token, signed with the shared bot secret, to verify authenticity
Required to be true for the API request to pass
Request body
Response
Bot features returned
Changes
- info
endpoint added
- info