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

# Lora API — Versioning & deprecation

> How the Lora API versions endpoints and announces deprecations.

## URL path versioning

Every stable endpoint is prefixed with `/v1/`. A breaking change ships under a new prefix (`/v2/`) rather than changing `/v1/` in place, so an integration pinned to `/v1/` keeps working indefinitely.

```text theme={null}
https://api.uselora.com/v1/shortcuts
```

## What counts as non-breaking

These can land in the current version without a prefix bump:

* New optional request fields
* New response fields
* New endpoints
* New error `code` values

## What counts as breaking

These always ship under a new path prefix:

* Removing or renaming a field
* Changing a field's type or semantics
* Removing an endpoint or a scope

## Deprecation

A deprecated endpoint or field is announced here, in the developer docs, before removal — not silently dropped. Check this page (or the [OpenAPI spec](https://api.uselora.com/openapi.json)'s `info.description`) for the current status of anything you depend on.