#Changelog

Status: Available. The log has been kept since the first publication of the documentation.

Purpose: record changes to the public API contract and the documentation. Any breaking change and any deprecation is announced here at least 90 days before it takes effect (the Deprecation and Sunset headers duplicate the entry in API responses; see Conventions).

#Versioning policy

#Entry format

Each entry contains the date, the affected area, and the type of change: added, changed, deprecated, removed, fixed, security.

#2026-10-12 — writing conversations, widget v2, personal data fields and data protection

API

• Added: writing conversations — POST /conversations (with Idempotency-Key, external_customer_id scoped to the integration, 201 on creation and 200 on replay), POST /conversations/{id}/messages with the ai_reply parameter (auto or none), the 202 response with an operation object and the ?wait wait of up to 20 seconds, AI refusal reasons and the queued_for_review flag, GET /operations/{id}, the errors 409, 429, 402, 503. Details are in Server Conversations API.
• Added: attachments and cards in messages; POST /conversations/{id}/cards sends a card into a conversation; conversation events in webhooks.
• Added: GET /channels/{id}/widget and PATCH /channels/{id}/widget for widget settings (assistant name, queue, icons, footer label, files); GET/POST/PATCH/DELETE /cards for product and item cards.
• Added: the fields= parameter in the read methods for conversations, messages, and leads. Without it, personal data is not returned; an unknown field name gives 422 unknown_field. See Data Minimization and Field Selection.
• Added (cells EN and ID only): the JWE format for personal data fields, PUT /me/encryption-key, the modes off, optional, required, the Encryption-Key-Id header, the _enc list, the pii_encryption block in GET /me. See JWE Format for Personal Data Fields; the page does not exist on the RU cell.
• Changed: the webhook signature is now the platform's electronic signature (JWS, Ed25519, detached payload) instead of a shared secret, with the public key set at GET /.well-known/jwks.json, a 300-second verification window, and rotation by kid. Subscriptions no longer have secrets.
• Changed: the webhook delivery headers are named Webhook-Event-Id, Webhook-Event-Type, Webhook-Timestamp, Webhook-Signature; the wallet state header is Wallet-State.
• Removed: the shared-secret (HMAC) webhook signature and the subscription secret rotation route (rotate-secret). Recipients verify the signature against the JWKS; Node.js, PHP, and Python examples are in Webhooks.

Widget

• Added: launching from your own button (data-launcher), branding (assistant name and subtitle, queue state, icons, footer label), header states ai, queued, operator, files from the visitor and the operator, cards with buttons. The window.Sapport object with methods, events, and a call queue before load; identify is not available yet. Details: Embedding the Chat Widget, Widget JS API, Client Chat API.

Documentation

• Added: the pages Data Minimization and Field Selection, JWE Format for Personal Data Fields (cells EN and ID), Protecting Personal Data from Leaking into AI Models, Data Protection by Cell.
• Changed: the pages on writing conversations and the AI seller on your own channel now match the implementation; the "Planned" label is removed where the feature has shipped.
• Changed: the chat templates in the gallery show the conversation state, operator name, attachments, and cards.

#2026-10-11 — server API: reading, wallet, webhooks v2

API

• Added: GET /me, GET /wallet; webhooks v2 (subscriptions, signing, retries, delivery log).
• Added: reading conversations and messages (GET /conversations, GET /conversations/{id}, GET /conversations/{id}/messages).
• Added: reading analytics (/analytics/timeseries, /analytics/traffic-sources, /analytics/funnel, /analytics/visibility) and dashboards (/dashboards/overview, /dashboards/pulse).
• Added: reading leads (GET /leads, GET /leads/{id}), articles (GET /articles, GET /articles/{id}), and strategist reports, topics, and actions.
• Still "Planned": writing (replies in conversations, editing leads and articles, decisions on topics and actions), events and offline conversions, article generation, the strategist chat, the status map, the widget JS API v2, test keys and the sandbox, GET /disclosures.

Documentation

• Changed: page statuses moved from "Planned" to "Available" for the released endpoints; response fields were checked against the implementation.
• The "Available" status takes effect with the deployment to a cell and the application of its migrations; a read that depends on a migration answers 503 until then.

#2026-10-11 — first edition of the documentation

Documentation

• Added: the documentation structure and the cross-cutting sections: introduction, quickstart, authentication, cells and data, conventions, webhooks, changelog, glossary.
• Added: a description of the existing client interfaces: the chat widget, the Chat API, the loader, the JS tracker, the server beacon and the CMS modules, and the article publisher through the connector (status "Available"; details are in the chat/, analytics/, and articles/ sections).
• Added: a description of the server API authenticated by a secret key (status "Planned"): integrations and keys, scopes, conversations and the AI seller, leads and the external CRM, analytics and dashboards, articles, the strategist, webhooks v2.

API

The v1 server API has not been released yet: there have been no contract changes. Until the OpenAPI specification is published, the response examples are illustrative.

#Planned platform changes that affect integrators

The entries below are warnings about what will change, not a log of completed changes.

#How to follow changes

• Subscribe to dashboard notifications: the tenant owner receives messages about key issuance, rotation, and imminent expiry; the api_key.expiring event arrives 30 and 7 days before expiry.
• Read the Deprecation and Sunset headers in API responses: automate logging them on your side.
• Check this log periodically.