Changelog

What changed in the public API.

How we change the API

Additions break nothing and ship without notice. A new field in a response, a new optional parameter, a new method, a new webhook event — any of these can appear at any time. Your code should tolerate fields it does not know.

Breaking changes mean a new version — /v2/. The old version lives for at least six months after the new one ships, and we announce it in advance.

What counts as breaking: removing or renaming a field, a method, an error code, a scope or a webhook event; adding a required request field; changing a field's type.

v1.4.0 — 13 September 2026

Connecting an assistant got simpler. Existing connections keep working.

• No key is needed to connect. You sign in as yourself and the assistant

acts with your permissions — including a narrowed dialog visibility if you have one. Before this you had to create a key and tick thirteen boxes first.

• The connection's permission is a «Read» / «Read and write» switch, changed in

the console without reconnecting.

• A key remains for one case: giving an assistant less than you have. It is

a folded line on the consent screen.

• One address. /mcp/readonly keeps working for anyone who already pasted it,

but it is gone from the console: the switch does the same thing more clearly.

v1.3.0 — 13 September 2026

Our own MCP server. An addition: nothing in the REST surface changed.

• Two addresses: /mcp — everything the key allows — and /mcp/readonly,

reading only, where no action is available even to a key that allows one.

• 19 tools shaped as whole tasks rather than as API methods. The list an

application sees is assembled for the one key it holds: what the key does not allow is not in the list.

• Sign-in over OAuth 2.1 with PKCE — the application registers itself, a

person in the console picks a key and approves. An ordinary API key in the header works too, without the consent screen.

• A reply to a customer is not sent straight away: the tool returns a link

where a person sees the exact text and presses Send. The check is on our side and cannot be bypassed.

• Text a customer wrote reaches the model marked as someone else's.
• Connected applications are listed in Settings → API & MCP and disconnect with one

button.

Details in the guide «Connect an assistant (MCP)».

v1.2.0 — 13 September 2026

Writing to the help centre, and meetings. Additive: nothing existing changed.

• A kb:write scope — create and edit articles and categories. The body is

accepted as Markdown. There is no delete, and the key holds no permission for one: removing published content stays a person's decision in the app.

• A new article is created as a draft. Publishing is a separate parameter, and

it is also what puts the article into the AI operator's index.

• A conferences:read scope — meetings with their summaries, decisions and

transcripts. Asks for both the meetings and the transcript permission.

• Two webhook events: conference.ended (the call finished — always) and

conference.transcript_ready (transcript and summary ready — only where there was a recording).

See the «Writing to the help centre» and «Meetings» guides.

v1.1.0 — 13 September 2026

Analytics. Additive: nothing existing changed or was removed.

• A new analytics:read scope. It covers the money reports too, so only

someone who holds both analytics and revenue rights — and who sees every conversation — can create such a key.

• Seven reports: overview, channels, teams, operators, revenue, dialog quality

and the AI operator. Plus filters, which returns the values the filters accept.

• Every report takes the same parameters: a from/to period and filters by

channel, team and operator. The period must not exceed 366 days.

• No cursor in reports: a report is a whole answer, not a page of a list.

See the «Analytics» guide for the details.

v1.0.0 — 12 September 2026

The first release.

• Project-level keys with resource:verb scopes.
• Reading: conversations, messages, contacts, client organizations, tags, users, teams, help center.
• Writing: conversation status and assignment, tags, replies and internal notes, creating and editing contacts and organizations.
• Webhooks: eight events, HMAC-SHA256 signatures, retries, a 7-day delivery log.
• Cursor pagination, one error envelope with a request id, Idempotency-Key, rate limits with headers.