Kore.ai

Prerequisites

You need:

A Kore.ai bot with a Webhook channel configured (Bot Builder → Channels & Flows → Webhook).
The Webhook channel’s app credentials with HS256 as the JWT signing algorithm. RS256 is not supported.
A Bluejay account.

If your Kore.ai tenant is on an internal network (private IPs like 10.x.x.x resolving via DNS), Bluejay must be able to reach the host. Test reachability from a public network with curl https://<your-kore-host>/ before configuring the integration. Internal-only tenants require a VPN tunnel or a publicly reachable Kore endpoint.

Setting Up the Integration

Collect Kore.ai credentials

In the Kore.ai Bot Builder, go to Channels & Flows → Webhook → Configurations. From the panel, copy:

Field	Example	Notes
Host URL	`https://platform.kore.ai`	The Kore.ai platform domain — just the host, no path.
Bot ID	`st-d536681d-57be-5068-88e3-eb4b9644b9a8`	Shown as “Bot Id”.
Client ID	`cs-8167aff9-e1ed-5ff3-9d27-12d09462ff27`	Shown under the Webhook channel’s app.
Client Secret	(hidden)	Click Display to reveal. Treat as a secret. Must be paired with HS256.

Do not paste the full Post URL (https://.../chatbot/v2/webhook/<bot_id>) into the Kore Host field — Bluejay appends the path automatically and you’ll get a 404. The Host field is just the platform domain.

Create the agent in Bluejay

Use the Add Agent endpoint and pass connection_type: "KORE" with all four Kore fields:

curl -X POST https://api.getbluejay.ai/v1/add-agent \
  -H "X-API-Key: your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Kore Support Bot",
    "type": "INBOUND",
    "mode": "TEXT",
    "connection_type": "KORE",
    "system_prompt": "...",
    "knowledge_base": "",
    "goals": [],
    "kore_host": "https://platform.kore.ai",
    "kore_bot_id": "st-d536681d-57be-5068-88e3-eb4b9644b9a8",
    "kore_client_id": "cs-8167aff9-e1ed-5ff3-9d27-12d09462ff27",
    "kore_client_secret": "<HS256 secret>"
  }'

Then call /v1/generate-kore-inbound-token with the returned agent_id to receive the plaintext access token (shown once).

Configure Bluejay's Webhook URL in Kore.ai

Back in the Kore.ai Bot Builder → Channels & Flows → Webhook → Configurations:

Set Integration Mode to Asynchronous.
Paste Bluejay’s Webhook URL into the Post URL field. The URL format is:
https://api.getbluejay.ai/v1/kore-webhook/<agent_id>
Paste Bluejay’s Access Token into the Access Token field.
Save, then Publish the bot.

The Webhook channel will not fire until the bot is published. If you re-publish later, the existing URL and Access Token stay valid — you don’t need to rotate them.

Run a simulation

Website
API

In Bluejay, open Agents & Simulations and select the agent you connected above. Create a simulation, add Digital Humans with scenarios and success criteria, then click Create and start to queue a run.

Use the Queue HTTP Text Simulation Run endpoint — Kore agents route through the same simulation queue as HTTP webhook agents.

curl -X POST https://api.getbluejay.ai/v1/queue-http-text-simulation-run \
  -H "X-API-Key: your-api-key" \
  -H "Content-Type: application/json" \
  -d '{ "simulation_id": "<id>" }'

Rotating credentials

Access Token — click Regenerate access token in Bluejay’s Connection Settings. The old token is invalidated immediately; re-paste the new one into Kore.ai.
Client Secret — update it in both Kore.ai (regenerate on Kore’s side) and Bluejay (paste the new value into Client Secret on the agent’s Connection Settings).

Troubleshooting

Symptom	Likely cause	Fix
`[KORE→] httpx error … type=ConnectTimeout`	Kore host unreachable from Bluejay’s network (private IPs / firewall)	Use a publicly reachable Kore tenant, or arrange a network tunnel
`[KORE→] response status=401 invalid access token`	JWT rejected by Kore	Verify Client ID and Client Secret match the Webhook channel exactly, and the channel uses HS256
`[KORE→] response status=404`	Bot ID wrong, or bot not published	Check `kore_bot_id`; ensure the bot was published after enabling the Webhook channel
URL contains `/chatbot/v2/webhook/...` doubled	`kore_host` was set to the full Post URL instead of just the host	Edit Kore Host to just `https://<platform>`
Inbound `POST /v1/kore-webhook/{id}` returns 401	Access Token in Kore doesn’t match Bluejay’s encrypted token	Click Regenerate access token in Bluejay and re-paste in Kore
Bot replies appear in Kore but never reach Bluejay	Webhook channel set to Synchronous instead of Asynchronous	Switch to Asynchronous and re-publish

Getting Started

Key Concepts

Test

Monitor

Integrations

Prerequisites

Setting Up the Integration

Rotating credentials

Troubleshooting

​Prerequisites

​Setting Up the Integration

​Rotating credentials

​Troubleshooting

Prerequisites

Setting Up the Integration

Rotating credentials

Troubleshooting