> For the complete documentation index, see [llms.txt](https://docs.autoenhance.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autoenhance.ai/api-versions.md).

# API Versioning

Autoenhance releases API improvements through dated versions, so you can choose when to upgrade.

Our API is **versioned by date**. Each version is a snapshot of how the API behaves on the day it was released. Your account is pinned to one version, so your integration keeps working exactly the same way until **you** decide to upgrade.

{% hint style="info" %}
**Latest version:** `2026-10-01`

To see what changed in each version, read our [Release notes](https://docs.autoenhance.ai/release-notes/). Every entry that needs a particular version says which one.
{% endhint %}

## How it works

1. **You're pinned when you sign up.** Your account uses the version that's current when you join, and every request you make is served by it.
2. **New versions don't affect you.** When we release a new version, any breaking change stays in that version. If a new version renames a field, we translate it for older versions, so your existing code doesn't need to change.
3. **You upgrade when you're ready.** New features become available once your account is on the version that introduced them, or a later one.

{% hint style="warning" %}
A few changes apply to every version, for example automatic upgrades from retired AI versions. The release notes say clearly when that's the case.
{% endhint %}

## Check which version you're on

Every API response includes an `x-api-version` header showing the version that served the request.

```http
x-api-version: 2025-08-31
```

## Try a newer version

Send the `x-api-version` header with the version you want to test:

```http
x-api-version: 2026-10-01
```

This applies to that request only, so you can try a newer version without changing your account.

## Upgrade your account

1. Read the [Release notes](https://docs.autoenhance.ai/release-notes/) for every version between yours and the one you want. Look for entries marked **Action needed**.
2. Test your integration by sending the new version in the `x-api-version` header.
3. When everything works, contact support to pin your account to the new version.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.autoenhance.ai/api-versions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
