Versioning

Flora Codex versions its API in the URL: /v1, /v2, and /v3. You pick one when you start and code against it. A version is a stable contract: its response shape does not change once it is in use, so an integration written against /v2 keeps working as the data underneath it grows. A change that would break that contract goes into a new version, never into an existing one.

Which version

v2 is the current version, and where new work should start. v1 is the original surface, now deprecated; if you are on it, the migration guide covers the move. v3 is a closed preview, and not a target yet.

Lifecycle

A version stays supported until it is formally deprecated, always with a published sunset date announced well ahead of removal. A deprecated version keeps working until that date and signals its status in its response headers, so a client can notice without hard-coding anything. v1 is the only deprecated version today, with a sunset of 31 January 2027.

Deprecations tracks what is scheduled and when; the changelog records what has shipped.