> For the complete documentation index, see [llms.txt](https://api-reference.usecommune.dev/llms.txt)

# Versioning

The base URL carries no version segment. A request selects a contract
version with the `Commune-Version` header, whose value is the release date
of the contract (for example `2026-08-26`). Omitting the header pins the
request to the version that was current when the API key was issued.

Every response echoes the version it resolved to in a `Commune-Version`
response header, on success and on failure alike. A client that never sets
the header can read which contract it has been getting, and compare it
against `version` in `GET /status` to find out whether a newer one is
available to move to.

Every response also carries a `Commune-Request-Id`, which is the value that
appears as `request_id` in an error body. Quote it in support requests.

A version has changed after its release date only while the API is
pre-release, and each such change is listed under Removals.

## Example
Pin the contract on the request:

```http
GET /newsletters HTTP/1.1
Host: api.usecommune.com
Authorization: Bearer cmn_sk_...
Commune-Version: 2026-08-26
```

Every response says which version answered, and which request it
was:

```http
HTTP/1.1 200 OK
Commune-Version: 2026-08-26
Commune-Request-Id: req_6f1c0e9b2d8a4f7c9e3b5a1d0c8f2e4b
```

