Interaction Store

PUT /api/v1/settings/interaction-store

Update the interaction store backend. This changes the storage engine used for new interaction history writes.

Request Body

Field	Type	Required	Description
`backend`	string	Yes	One of: `postgresql`, `keyspaces`, `scylla`, `dynamodb`

Backend Options

Backend	Description
`postgresql`	Default. Standard PostgreSQL storage with partition support.
`keyspaces`	Amazon Keyspaces (managed Cassandra). High-throughput write-heavy workloads.
`scylla`	ScyllaDB. Low-latency, high-throughput Cassandra-compatible storage.
`dynamodb`	Amazon DynamoDB. Serverless, auto-scaling NoSQL storage.

Example

curl -X PUT https://playground.kaireonai.com/api/v1/settings/interaction-store \
  -H "Content-Type: application/json" \
  -H "X-Tenant-Id: my-tenant" \
  -d '{ "backend": "keyspaces" }'

Response

{
  "backend": "keyspaces",
  "allowedBackends": ["postgresql", "keyspaces", "scylla", "dynamodb"]
}

Error Codes

Code	Reason
`400`	Invalid backend value

Changing the backend does not migrate existing data. Historical interactions remain in the previous backend. Plan a data migration separately when switching backends in production.

Roles

admin only

Overview

Decisioning

Studio

Data

Algorithms & Models

Content & Metrics

Orchestration

Customers & Traces

Events & Attribution

Analytics

AI

Testing & Simulation

Export & Import

Admin

Integrations

GET /api/v1/settings/interaction-store

Response

Roles

PUT /api/v1/settings/interaction-store

Request Body

Backend Options

Example

Response

Error Codes

Roles

​GET /api/v1/settings/interaction-store

​Response

​Roles

​PUT /api/v1/settings/interaction-store

​Request Body

​Backend Options

​Example

​Response

​Error Codes

​Roles

GET /api/v1/settings/interaction-store

Response

Roles

PUT /api/v1/settings/interaction-store

Request Body

Backend Options

Example

Response

Error Codes

Roles