For developers

Web Chat v4

A white-label widget with multiple tickets, signed context, and backward compatibility.

Updated: August 11, 2026

Installation

htmlKanyman docs

<script
  src="https://app.kanyman.ru/kanyman-chat.v6.js"
  data-public-key="wc_pk_..."
  defer
></script>

Add the page’s exact Origin to the Web Chat settings. The public key is visible in HTML and is not a secret, but it must belong to the selected channel.

White-label appearance

The name, logo, primary color, and copy are configured in the Web Chat channel of the specific project. Visitors do not see mandatory Kanyman branding; if the logo is missing or fails to load, a neutral chat icon is used.

Passing context

javascriptKanyman docs

window.addEventListener("load", function () {
  window.KenymanChat.open({ contextToken });
});

// After the page or selected object changes:
window.KenymanChat.setContextToken(nextContextToken);

Lifecycle

Session creation with context uses an Idempotency-Key.
Context is updated through setContextToken and the session PUT endpoint.
Invalid or expired context does not block ordinary chat.
The chat session token remains in sessionStorage as in the previous version.
Published v1–v3 versions do not change; the current white-label runtime is v4.

Content Security Policy

textKanyman docs

script-src 'self' https://app.kanyman.ru;
connect-src 'self' https://app.kanyman.ru;
img-src 'self' https://app.kanyman.ru data:;

Continue reading

Signed contextJWT envelope, JSON Schema, signatures, and replay protection.API and errorsPublic Web Chat endpoints and safe error codes.Security and launchChecklist for keys, tokens, network restrictions, and production UAT.