Versioning

The three API surfaces are versioned independently. The Channel API may evolve slowly — messaging is a stable interface. The Platform API may evolve more quickly as orchestration capabilities expand. The Integration API may evolve as the tool registration model matures.

Version Path

All endpoints are prefixed with a version segment:

`` https://api.thinklio.com/v1/channels/{channel_id}/messages ``

The current version for all surfaces is v1.

Stability Guarantees

Within a major version, Thinklio guarantees:

  • No removal of existing fields from response bodies
  • No change to the meaning of existing fields
  • No change to the behaviour of existing endpoints in a breaking way

Additive changes (new optional fields, new endpoints) are made within the current version without a version bump.

Breaking Changes

A breaking change always introduces a new major version (/v2/) and a deprecation period of at least six months for the previous version. During the deprecation period, both versions are supported. Deprecated versions are announced via:

  • Email to API key owners
  • A Sunset response header on deprecated endpoints
  • Dashboard notifications

Version Negotiation

You may pin to a specific API version using the Thinklio-Version header. If omitted, the latest stable version is used.

``http Thinklio-Version: 2026-03-01 ``

Date-based versioning lets you lock behaviour to a specific release date, independent of major version increments.