# Vikka Studio API versioning and deprecation policy

> Status: API v1 is active. It is not deprecated and has no scheduled sunset.

## Versioning

Vikka puts the major API version in the URL, for example `/api/v1/services`. Compatible additions may be made inside v1 when they do not remove fields, change established meanings, or require an existing client to change. A breaking contract change receives a new major path such as `/api/v2`.

The unversioned `/api` endpoint is a discovery index. Agents should integrate against the versioned resource URLs listed there or in the OpenAPI document.

## Deprecation notice

Vikka aims to give at least 180 days of public notice before retiring a stable major API version. When a version becomes deprecated, its responses will include the RFC 9745 `Deprecation` header with a Structured Field date and a `Link` header whose relation is `deprecation`, pointing to migration guidance.

If a final shutdown date is scheduled, responses will also include the RFC 8594 `Sunset` header as an HTTP date. `Sunset` is only sent when that date exists; it is not sent on the active v1 API today.

A severe security, legal, or abuse issue may require a shorter timeline. Vikka will document the reason and the safest available migration path if that exception occurs.

## Current resources

- OpenAPI contract: https://www.vikka.studio/openapi.json
- Developer guide: https://www.vikka.studio/developers
- API index: https://www.vikka.studio/api