Kliki documentation

Kliki helps teams create isolated recommendation instances, send interaction events, and request personalized results from one platform.

How it works

Workspace, event, and recommendation flow

Each workspace owns a unique API key and a dedicated instance. You send events into that instance, then request recommendations back from the same tenant.

  • Every workspace is isolated.
  • Events and recommendations use the same instance id.
  • Dashboard pages show live status and endpoints.

Quickstart

Provision a workspace, create an instance, and start sending events in three steps.

Create a workspace

Register the account that owns your recommendation data.

Create an instance

Assign a tier, platform, and API key to one deployment.

Send events

Track views, clicks, and purchases through the API.

Instance setup

Each instance receives its own API key, endpoint URL, and live status view inside the dashboard.

Event ingestion

Use the ingestion flow to send views, clicks, add-to-cart actions, and purchases into the correct instance.

REST API reference

Use the REST API to create instances, inject events, and fetch recommendations for a user or session.

POST/api/v1/instances/:instanceId/inject
GET/api/v1/instances/:instanceId/recommend?userId=&limit=
{
  "userId": "usr_789",
  "itemId": "itm_456",
  "actionType": "view",
  "sessionId": "sess_001",
  "metadata": { "platform": "web" }
}

Workspaces

A workspace is the isolated runtime for a single recommendation deployment. Each instance has its own key, status, and event stream.