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

# API versioning

> How Text API versions work, what each stage means, and what to do at each one.

Text APIs are versioned. Each version moves through a fixed lifecycle — from early access to eventual decommission. Knowing where a version sits in that cycle tells you how stable it is and whether you need to act.

**Use the stable version for any new integration.** You can see which stage a version is in from the version selector in the API reference.

## API versions lifecycle

<Steps>
  <Step title="Developer preview" id="developer-preview">
    A preview of features currently in development. The API surface may change without notice and access is limited — [contact us](mailto:developers@text.com) to request it.

    **Duration:** \~6–7 months.
  </Step>

  <Step title="Stable" id="stable">
    The feature set is closed and the version is publicly available. All bug fixes are applied here. This is the version to build on.

    **Duration:** \~6–7 months.
  </Step>

  <Step title="Legacy" id="legacy">
    A newer stable version has been released. This version still works but only receives critical and security fixes. Responses include a `Legacy` header with the end date in `YYYY-MM-DD` format.

    **What to do:** start migrating to the current stable version before the legacy period ends.

    **Duration:** \~1–1.5 years.
  </Step>

  <Step title="Deprecated" id="deprecated">
    The version is nearing decommission. Only critical and security fixes are applied. Responses include a `Deprecation` header with the end date in `YYYY-MM-DD` format.

    **What to do:** migrate immediately — the version will stop working when the deprecation period ends.

    **Duration:** \~3–6 months.
  </Step>
</Steps>

## Currently versioned APIs

| API                | Dev preview | Stable | Legacy |
| ------------------ | ----------- | ------ | ------ |
| Agent Chat API     | v3.7        | v3.6   | v3.5   |
| Customer Chat API  | v3.7        | v3.6   | v3.5   |
| Configuration API  | v3.7        | v3.6   | v3.5   |
| Reports API        | v3.7        | v3.6   | v3.5   |
| Webhooks           | v3.7        | v3.6   | v3.5   |
| Chat Widget JS API | —           | v5.0   | v4.0   |

<Info>
  Not all Text APIs use this versioning model. Some APIs — like the Customer
  Data Platform, Partner, and Global Accounts APIs — operate under a single
  continuously updated version. Breaking changes to these APIs are announced in
  the [changelog](/api/changelog).
</Info>