Koltrix logoKoltrixDocs
Help

Changelog

Changes that affect developers: the REST API, the SMTP relay, webhooks, domain setup and these docs. Newest first. For new features in the Koltrix app, see the product changelog.

/api/v2 is the stable API. Changes to it are additive: new fields and endpoints may appear, but existing fields, status codes and behaviour don't change without a new version and notice.

2026-10-21

Extra storage packages. Workspaces on Starter and Pro can add one storage package (+5 GB, +20 GB or +50 GB) from Settings → Billing. GET /api/v1/billing/subscription now also returns storage_units, storage_extra_bytes and storage_addon_available, GET /api/v1/billing/plans lists each plan's storage_extra packages, and POST /api/v1/billing/storage changes the package. The workspace's storage limit includes the package it pays for. See Limits and quotas.

2026-10-20

Extra mailboxes. Workspaces can add mailboxes beyond their plan's own, from Settings → Billing. GET /api/v1/billing/subscription now also returns extra_addresses, addresses_included, addresses_max_extra and mailbox_addon_available, and the workspace's address limit (402 with kind: addresses) includes the extra mailboxes it pays for. See Limits and quotas.

  • /api/v2 is unchanged.

2026-10-17

Docs and site. Every blog post has a Markdown version at /blog/<slug>.md, and /llms-full.txt lists the full site for AI search tools. Checkout now opens with the buyer's email filled in.

  • /api/v2 is unchanged.

2026-10-16

Faster pages. Docs and site images and logos are cached for longer, and Permissions-Policy no longer lists the retired interest-cohort token.

  • /api/v2 is unchanged.

2026-10-15

Domain setup comes first. A new workspace opens onto the setup wizard until a sending domain is verified, and the rest of the app stays closed until then. Owners and admins finish the setup; other members see a waiting screen. Existing workspaces with a verified domain are unaffected, and removing a domain later does not lock you out. See Quickstart. Sign in with Google is now available on the sign-in and sign-up pages.

  • /api/v2 is unchanged.

2026-10-14

Mailbox photos and BIMI setup. New page: Logo in inboxes (BIMI). Each address can have a photo, shown across Koltrix and on mail you send. A new BIMI section in Settings → Domains & addresses hosts your logo, validates it, shows the DNS record and checks DMARC, the record and the certificate. Koltrix never writes your DNS and never fetches an address you type.

  • /api/v2 is unchanged.

2026-10-13

Team guide and assistant tools for teams. New page: Working as a team, covering roles, invitations, groups, assigning conversations, internal notes and @mentions, who is viewing, views, suspending and removing members, transferring ownership, activity and insights.

  • MCP: three tools for teamwork, team_list_members, thread_assign and thread_add_note. None of them sends email, so none needs an approval card. Each is audited and rate-limited. See Connect an assistant.
  • /api/v2 is unchanged.

2026-10-12

API, relay and webhook fixes. Found by running every documented endpoint, sample and error against a test copy of the service.

  • POST /api/v2/emails: every recipient is checked before anything is queued (a bad one is a 400 that names it), names are accepted (Ada <[email protected]>), international domains are converted, at most 1,000 recipients per request, and line breaks in a subject become spaces. A retry with the same Idempotency-Key is answered even after your quota runs out. Message records are tied to their send by id: two sends with the same subject no longer mark each other sent. One refused recipient no longer fails the others, a recipient on your suppression list now ends as bounced with the reason (its record used to say sent), and a temporary failure is retried for about an hour before the message is marked bounced (it used to be marked bounced on every attempt).
  • Errors: an unknown /api/v2 path is a JSON 404 (it was a 401), malformed ids are 404s, database messages are no longer shown in 500 bodies, limit above the maximum is clamped, GET …/events of an unknown message is 404, and POST /sequences requires list_id and the subscribe trigger, as documented. Adding or importing subscribers through the API counts against the plan's contacts allowance (402).
  • SMTP relay: bodies sent quoted-printable or base64 (what Nodemailer, PHPMailer and Python produce for real HTML) are decoded instead of arriving garbled; multipart/alternative works; attachments are refused with 554 5.6.0 instead of being damaged; a connection can no longer exhaust the relay's memory with an endless line; a second AUTH is refused; five failed logins close the connection.
  • Webhooks: endpoints must be https:// and public. An endpoint pointing at a private or cloud-metadata address is refused when added and never contacted. A webhook's delivery log can only be read by its own workspace, PATCH with only active pauses an endpoint, and Send test goes to the endpoint you chose. Settings → Webhooks now shows the signing secret.
  • API keys: unknown scopes are refused, a key created with no scopes gets read and send, Bearer is accepted in any capitalisation, and the keys of a suspended workspace are refused with 403.
  • Docs: the Node.js and Python samples for the delete endpoints no longer fail on the empty 204 body, and the Node.js webhook sample is plain JavaScript.

2026-10-09

AI assistants: tab counts. get_inbox_summary now also returns unread_by_tab (primary, updates, promotions, newsletters, cold), the same five tabs as the inbox. Mail written by a person, and account mail that needs action such as verification links and security alerts, is counted in Primary. unread_by_category is still returned. See AI assistants.

2026-10-06

Delete an email address. Owners and admins can delete an address from Domains & addresses. It stops receiving mail (senders get an unknown-recipient rejection) and the messages it already received are kept. The last address of a workspace and postmaster@ can't be deleted, and the same address can be created again later.

AI assistants setup page. The page in the app is now called Connect AI apps and has its own entry in the sidebar. The docs refer to it by that name.

2026-10-04

Interactive cards in AI assistants. In an app that supports the MCP Apps extension, list_mailboxes, search_mail, list_threads, get_inbox_summary, get_thread and create_draft now also show a card: a mailbox picker, a conversation list, a plain-text conversation view and a draft review card with Send, Edit in Koltrix and Discard. The server offers cards only to an app that declares MCP Apps support (io.modelcontextprotocol/ui) when it connects, and serves the pages as ui://koltrix/* resources; other apps get exactly the text results they had. For an app that shows cards, sending moves to the Send button: send_draft is not offered, and the card calls a new app-only tool, send_draft_from_card, with a one-time token (30 minutes, single use, bound to the draft, the connection and the text shown) delivered only to the card. Every send check and limit is unchanged. Cards load nothing from the internet and show mail content as plain text. See Interactive cards.

2026-10-03

AI assistants (MCP). Connect Claude, ChatGPT, Cursor and other MCP apps to your Koltrix inbox at https://mcp.koltrix.com/mcp. Assistants can search, read, organise and draft; they can't forward or permanently delete mail. Sign-in is OAuth, with per-connection permissions, revocation and an admin switch. See AI assistants.

AI assistants can send, if you allow it. A new send_draft tool sends a draft you already have, but only when a workspace owner or admin has turned on Allow assistants to send email after you confirm (off by default), you have opted in with the new mail.send permission when connecting, and the assistant has shown you the message and got your yes. The call must carry confirmed: true and a confirmation of the form [email protected], [email protected] | Subject matching the draft's recipients and subject. Limits: 10 recipients per message, 20 sends a day per connection and 50 a day per workspace. Connections made before this can't send until they are reconnected with the box ticked. Koltrix's own AI in the app is unchanged: it never sends without a click. See Sending email from an assistant.

Docs. Every page was checked against the API's code and corrected. New pages: Errors, Deliverability and suppressions and this changelog. Known gaps are now marked "Current limitation" where they apply.

2026-10-02

Five DNS records for new domains. A new domain now asks for an ownership record (_koltrix), MX, SPF (include:_spf.koltrix.com), its own DKIM key (kx1._domainkey) and DMARC. If your domain already has an SPF record, Koltrix shows a merged one. Domains verified before this keep working unchanged and show the new records as a recommended upgrade; once their kx1._domainkey record checks out, their mail is signed with their own key automatically. See Custom domains and DNS.

Domain claims. A domain can be pending in more than one workspace, so nobody can block its real owner by adding it first. The first workspace whose own ownership record appears in DNS verifies it.

2026-10-01

Developers hub. API keys, SMTP settings, webhooks and delivery logs are gathered under Developers in the app, with a copy-and-run quickstart.

2026-09-29

Send quotas on the API and SMTP relay. Sends through POST /api/v2/emails and the SMTP relay count against your plan's API send allowance, per recipient. Over the allowance the API answers 429 with "code": "quota_exceeded" and resets_at, and the relay answers a temporary 452, so mail servers retry rather than drop the message. See Limits and quotas.

2026-09-01

Per-key rate limit. /api/v2 allows 60 requests per minute per API key and answers 429 with Retry-After above that.

2026-08-31

SMTP relay limits. At most 1,000 recipients per message (452 4.5.3 above that, so the rest can be sent in another message), and a message over 25 MB is refused with a permanent 552 5.3.4 instead of a retryable error.

2026-08-30

Idempotency without duplicates. The Idempotency-Key is claimed before a message is queued, so a retry that races the original can no longer send a second copy. A retry during the original answers 409; if the idempotency store is unavailable the API answers 503 and sends nothing.

Bounces that come back later. A permanent bounce report that arrives after the message was sent now marks the message bounced and adds the address to the suppression list.

Unsubscribes suppress. Unsubscribing, from a link or through the API, adds the address to the workspace's suppression list, so no list, sequence or transactional send mails it again.

2026-07-30

Display names in From. "from": "Acme <[email protected]>" is accepted by POST /api/v2/emails.