KonektDevelopersYour API keys

Changelog

Changes to the public API and the MCP server are listed here, newest first. We only add: a field, an operation or an error code may appear, and nothing is renamed or removed without notice on this page first. Write your client to ignore fields it does not know.

November 2026, disconnecting an account keeps everything

  • accounts_disconnect disconnects an account and keeps its conversations, messages, send history and the people waiting on it, for 180 days. It returns kept_until and the counts it touched. mode: erase is refused with person_required. accounts_removal_impact reads the counts first and accounts_waiting_leads lists the people waiting on an account.
  • campaigns_move_waiting_leads takes include_messaged and campaign_id, moves people from a disconnected account, and answers with messaged_moved. campaigns_rerun_leads runs people stopped because their account was removed again from another account. Both are contact operations.
  • accounts_list and accounts_get show disconnected accounts and carry disconnected, kept_until, reconnect_needs_person and reconnect_hint. Connecting an account again needs a person with the browser extension.

November 2026, plug and play for agents

  • One connection, full access. An assistant that signs in, and a key, act as the person with everything they may do, and contact operations run at once through the same rules as the app. The choice between asking first and acting at once is gone; the consent page has one button, Allow, and a small link, Limit to read only. What stays with people is listed in Authentication and keys.
  • The only approval left is a switch of the workspace, Require approval for what agents send, off by default. See Contacting people.
  • get_started and account_status tell an agent who it acts for, which workspaces and accounts it can use and how much each may still send. The server sends a briefing when a client connects.
  • import_leads (up to 5000 leads in one call), create_campaign_with_sequence (steps, accounts and leads in one call) and inbox_overview.
  • A connection with one workspace never names it. With several, the error lists the allowed ids.
  • The idempotency key is optional everywhere, and over MCP it is derived for you. The same text into the same conversation within ten minutes returns the first message.
  • Every error has a hint, a validation error lists the allowed values, and a refused contact operation carries detail and retry_at. New code person_required.
  • Billing reads (billing_summary, billing_overview, organization credentials) and erasing a lead on a privacy request (leads_erase_preview, leads_erase) are operations.
  • Inviting, removing and changing the role of members, and which inboxes a member sees, are no longer operations: access control stays with people.
  • A complete OpenAPI 3.1 document at /api/v1/openapi.json and /.well-known/openapi.json, descriptions and examples on every tool and parameter, and /docs/llms.txt and /docs/llms-full.txt for agents. An OAuth access token now also works at the REST API.

Earlier in November 2026

  • Operations that act on people: reply, retry a message, start, resume and change campaigns, move waiting leads, settle a review, resume an account, allow contact again, invite and remove members. At first they waited for a person's approval by default; that changed, see above. See Contacting people.
  • The approval queue: approvals_list and approvals_get.
  • The inbox: ask for an update and read where it stands, read older conversations and messages, and the reply email setting.
  • Members and invitations, message retention, the organization (create a workspace, rename), notifications, exports as CSV text, and the settings webhook (REST only).

Version 1

The first public version of the API and the MCP server.

  • Reads for workspaces, accounts, campaigns, templates, leads, lead lists, the do-not-contact list, the inbox and analytics.
  • Writes that contact nobody (the contact operations came later, see above): templates, lead lists, leads, CSV imports, campaign drafts, account and workspace settings, and inbox state.
  • The events feed and webhook endpoints with signed deliveries.
  • The MCP server at /api/mcp, with sign in for assistants and API keys for programs.
  • This documentation and the API reference, generated from the same list of operations that the API runs.