platform

Required.

Supported values:

• LITHIUM
• EXTERNAL (legacy value)

Use LITHIUM for all other networks.

Use EXTERNAL for legacy bots that are directly connected to Twitter or Facebook. This also includes Facebook Handover Protocol.

Note: EXTERNAL will support the legacy Bot API registration flow.

companyKey

Required. Your company key. this is the Analytics API Company Key located in your Response app under Account Admin > General Settings > Analytics API Settings. If you do not see the key, contact your Care administrator. You might not have the appropriate permissions.

networkKey

Required. The source channel for this registration.

Supported values:

• apple
• facebook
• googlemessages
• sms
• twitter
• wechat
• whatsapp
• brandmessenger (for current Khoros Brand Messenger)
• instagram
• lia (for Khoros Communities)

networkInstance

This is Required if you are using lia as your network. The value should be formatted as follows:

url/ with the trailing forward slash / at the end. For example:

“networkInstance”: “careinstance.lithium.com/”,

externalId

Required. The external identifier of the page or account on the external network for which the bot is being registered.

appId

Required. If platform LITHIUM, this is an internal identifier, determined by you, for your app. The ID is used by the Automation Framework. If you want to use the same bot for multiple networks, appId must be the same for each registration.

If platform EXTERNAL, this will be the app ID of the associated Facebook or Twitter app that is used by the bot. This is used as the unique identifier for the bot in Response.

name

Required. A user-friendly, customer-facing name, created by you, for the bot.

callbackUrl

Required. An endpoint to call to relay the incoming message from Care to the bot.

Note: If using the Facebook Handover Protocol, enter a dummy value. This field is not used by the Facebook Handover Protocol, but is still required by the call.

mode

Required. No default is set.

Supported values:

• LIVE
• MAINTENANCE
• MONITORING

When LIVE, all events are forwarded to the Bot Server via webhooks, and the bot can take any supported action. Only one LIVE bot can be supported on a specific network/externalId at one time.

When MAINTENANCE, no events are sent via webhooks. Any customer messages that arrive while in this mode are explicitly handed off to an AGENT, so that when the bot returns from MAINTENANCE mode, the bot will not start answering conversations already in progress.

When MONITORING, no responses are sent from the bot to the end-user. More information available in our Monitoring Bots guide.

Note: When mode is MAINTENANCE, you may still make API gateway requests, but you will be blocked from taking any bot action such as resolving a conversation, updating priority, etc...

credentials

Required. A credentials sub-object for passing authentication credentials to authenticate the bot webhook callback.

Fields include:

• type - The authentication type: HMAC or BASIC_AUTH.
• identity - the basic auth username or HMAC key. The username provided is used as the standard basic authentication header.
• secret - the authentication secret. Required for basic authentication and HMAC.

"credentials": {        "type": "HMAC

Note: If using the Facebook Handover Protocol, enter a dummy value. This field is not used by the Facebook Handover Protocol, but is still required by the call.

publicFilter

Optional. A publicFilter object used to indicate what types of public content should be forwarded to the bot webhook. If this is left null, only private content will be generated.

Fields include:

• includeTargeted - if set to true, then public messages that directly target the bot’s externalId are forwarded to the bot. This mainly applies to Twitter mentions.
• includeSourceTagIds - a list of source tag IDs to match. Any incoming message with a source tag that matches one specified in the list is forwarded to the bot webhook.

"publicFilter": {  "includeTargeted": true,  "includeSourceTagIds": [    999, 1002  ]}