> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trytikt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Versioning

> How TIKT changes its payloads without breaking your integrations.

Every event carries an `api_version`, a date. All destinations start on **`2026-10-01`**.

## What is not a new version

TIKT can, at any time and without notice:

* add a field to an object;
* add an event type — a destination listening to **All events** receives it;
* add a value to a field that has a list of values (a new `status`, a new `reason`).

**Ignore what you don't know.** Read the fields you need, accept extra ones, and treat an unknown value as “other”.

## What is a new version

Removing a field, renaming it, or changing its type is a **new version**:

* announced **six months** in advance;
* never imposed on a version in use: each destination keeps its version until its owner changes it.

## Changelog

| Version | Date | Changes |
| - | - | - |
| `2026-10-01` | October 2026 | First version: 34 events, the lead, signal, post, tracked profile, cycle, credits, ICP, destination and workflow objects. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.