Versions and changes
The API is versioned in its path, and v1 is stable — it grows without breaking what you built.
New endpoints, new optional fields, new values and new fields in answers arrive in /api/v1 as they are. Read answers tolerantly: ignore fields you don’t know, and expect new values in fields like status or transition. Every answer carries Kinetune-Api-Version: 1.
Nothing you rely on changes or disappears without notice. To remove or rename an endpoint, a field, a value, a CLI command or an MCP tool, we deprecate it first: it is marked in the API reference, the OpenAPI document (deprecated, x-sunset) and the MCP tool, its answers carry Deprecation and Sunset headers, and it keeps working at least 180 days. A redesign would come as /api/v2, with v1 kept running beside it.
The CLI and the n8n node follow semantic versioning: a minor version adds, a patch fixes, and only a major version can change how an existing command or node field works.
What changed, newest first, is in the changelog.