Khoros

Khoros Respond API

The Respond API from Khoros — 1 operation(s) for respond.

GitHub OpenAPI
Business capability
Customer Inquiry Management BC-430.10

Operations 1

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /respond Send a bot reply to an incoming message · Respond to incoming message (bot to channel) #
Ask an LLM
“How does a bot reply to a customer's incoming message on a channel?”
“Do I need a charset header for emoji in bot replies?”
Tell an agent
Respond to the incoming message with payload {payload}.
Send the bot's reply back to the customer's channel.

Documentation

📖
Documentation
https://developer.khoros.com/khoroscaredevdocs/docs/khoros-care-integration-overview
📖
Documentation
https://developer.khoros.com/khorosmarketingdevdocs/docs/developing-and-integrating-with-khoros-marketing
📖
Documentation
https://developer.khoros.com/khoros-flow/docs/overview-of-khoros-flow-apis

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/khoros-ai/refs/heads/main/openapi/khoros-ai-respond-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/khoros-ai:khoros-ai-respond-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

khoros-ai-respond-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: bot-api-v3 Respond API
  version: '1.1'
servers:
- url: https://api.app.lithium.com/bots/v3
security:
- {}
tags:
- name: Respond
paths:
  /respond:
    post:
      summary: Respond to incoming message (bot to channel)
      description: Respond to an incoming message (bot to channel)
      operationId: respond-post
      parameters:
      - name: charset
        in: header
        description: Add `charset=utf-8` if emoji support is required.
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                RAW_BODY:
                  type: string
                  description: A outgoing Message JSON payload (bot to channel). See payload details below.
                  format: json
      responses:
        '200':
          description: '200'
          content:
            application/json:
              examples:
                Result:
                  value: "{\n    \"data\":\n    {\n        \"messageId\": \"1315739291251000000\",\n        \"payloadType\": \"message\",\n        \"requestState\": \"SUCCESS\"\n    },\n    \"requestId\": \"example1-f0b0-4dbb-8b6d-c82192c2054a\"\n}"
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      messageId:
                        type: string
                        example: '1315739291251000000'
                      payloadType:
                        type: string
                        example: message
                      requestState:
                        type: string
                        example: SUCCESS
                  requestId:
                    type: string
                    example: example1-f0b0-4dbb-8b6d-c82192c2054a
        '202':
          description: '202'
          content:
            application/json:
              examples:
                Result:
                  value: HTTP/1.1 202 Accepted
        '400':
          description: '400'
          content:
            application/json:
              examples:
                Result:
                  value: "HTTP/1.1 400 Bad Request{  \n  \"error\":{  \n    \"messages\":[  \n      \"Invalid networkKey farcebook\"\n    ]\n  }\n}\n"
        '403':
          description: '403'
          content:
            application/json:
              examples:
                Result:
                  value: "HTTP/1.1 403 Forbidden{  \n  \"error\":{  \n    \"messages\":[  \n      \"This bot doesn't own the conversation <message coordinates>\"\n    ]\n  },\n  \"requestId\":\"some id\"\n}\n"
      deprecated: false
      security: []
      x-readme:
        code-samples:
        - language: curl
          code: "curl POST \\\n  https://api.app.lithium.com/bots/v3/respond \\\n  --data @/path/to/payload.json \\\n  -H \"Content-type: application/json; charset=utf-8\" \\\n  -H \"Authorization: Bearer [TOKEN]\"\n"
        samples-languages:
        - curl
      tags:
      - Respond
x-readme:
  headers:
  - key: Authorization
    value: Bearer [TOKEN]
  - key: Content-type
    value: application/json; charset=utf-8
  explorer-enabled: false
  proxy-enabled: true
x-readme-fauxas: true