Changelog
Changes to the partner interface land here, newest first, once there are any.
apiVersion v1 · schemaRevision 2
How the interface evolves
- Additive-only within v1
- New optional fields and entirely new tools are added at any time with no breaking change. An existing field never changes type, never becomes required, and never disappears. An existing tool never changes its output incompatibly and is never removed without the deprecation window below. A breaking change always gets a new version (/api/mcp/v2/) alongside v1, never an in-place break.
- 90-day deprecation window
- A tool or field slated for removal is first announced here as a dated entry, marked the same day with a deprecation note in its own description in tools/list, and then stays callable for at least 90 days. Removing it before the window expires is a contract violation; the window may only ever be extended.
- Version stamp cannot drift
- tools/list carries apiVersion and the same number the newest entry here declares. The Website build fails if the two disagree, so the tool reference and the changelog can never silently fall out of sync.
2026-09-13 · schemaRevision 2
Shipping methods and language
Quote, approval, send and scheduling accept destination catalog codes, including Swiss registered mail. Quotes list the current destination methods and English letter-format labels. Agents are instructed to explain shipping options in your chat language. Registered availability remains country and method specific; tracked mail is not registered mail.
Affects: shipping_quote, approval_submit, order_send, letter_schedule
2026-07-22 · schemaRevision 1
MCP template authoring (draft, release for solo partners, archive, discard)
Four new tools under the new template:write scope: template_save (write a draft), template_release (release), template_archive (archive) and template_draft_discard (discard an unreleased draft). Release via MCP only works when your partner account has exactly one active user; with several users a human still releases it in the dashboard (four-eyes principle), and the response then contains the link to the release screen. No hard delete: archiving is idempotent, and discarding only ever touches a version that has not been released yet, never a released or superseded one. The send path still only ever sees released versions, a draft can never end up in a letter. Kanzlei mode (X-FrankKi-Mode: kanzlei) still blocks all four tools. template_list and template_get can now additionally show open drafts with the template:write scope (statusFilter and versionId respectively), without changing the previous default. TEMPLATE_READONLY_VIA_MCP now applies more narrowly: it still fires for any template change outside these four tools, no longer for templates as a whole.
Affects: template_save, template_release, template_archive, template_draft_discard, template_list, template_get, TEMPLATE_SLUG_CONFLICT, TEMPLATE_VERSION_NOT_DRAFT, TEMPLATE_FOUR_EYES_REQUIRED, TEMPLATE_VERSION_IMMUTABLE, TEMPLATE_READONLY_VIA_MCP
Trust and live status
Machine-readable service facts and the current operational status of the partner interface are publicly available at all times, no login needed.