360Bots

Bots power menus, flows, OTP shells, and partner framework services.

List bots

GET /api/v1/bots

{
  "bots": [
    {
      "code": "portail",
      "name": "SEED Portail",
      "runtime_mode": "local",
      "partner": { "code": "seed", "name": "SEED" }
    }
  ]
}

Create a bot

POST /api/v1/bots

{
  "code": "support",
  "name": "Support bot",
  "runtime_mode": "service",
  "channel_inapp": true
}

Bot details

GET /api/v1/bots/{code}

Includes menus, flows, and actions when runtime_mode=local.

Sessions

GET /api/v1/bots/{code}/sessions

Inspect active sessions and their context for operations and debugging.

Framework service

A partner-managed HTTP service that implements business logic:

Endpoint	Purpose
GET /api/v1/bot-framework	Retrieve the current configuration
PUT /api/v1/bot-framework	Set service_base_url, authentication, and paths

When runtime_mode=service, MorisBox calls your /start and /input endpoints and maps their responses to client events.

Flow invitation

POST /api/v1/bots/{code}/flows/{flow_code}/invite - see Flows.

Per-bot credentials

Each bot has a hashed bot token and an HMAC webhook secret.
See Bot Credentials and Webhooks for the complete security model and API.