---
title: "lovefengis API versioning and deprecation policy"
description: "How lovefengis versions its REST API and MCP server, what counts as a breaking change, and how deprecation is announced with Deprecation, Sunset and Link headers."
canonical_url: https://lovefengis.com/gelistirici/surum-politikasi
last_updated: 2026-10-14
lang: tr
llms_txt: https://lovefengis.com/llms.txt
---

1. [Ana sayfa](https://lovefengis.com/)
2. [Developers](https://lovefengis.com/gelistirici)
3. lovefengis API versioning and deprecation policy

# lovefengis API versioning and deprecation policy

Son güncelleme: 14 Ekim 2026

This policy covers the lovefengis REST API (`/api/v1`), its OpenAPI description (`/openapi.json`) and the MCP server (`/mcp`). Current version: `v1`.

## 1\. Versions

- The major version is part of the path: `/api/v1`. A breaking change ships under a new path (`/api/v2`); the old path keeps working during its notice period.
- Clients may pin the version with the request header `API-Version: 1`. An unsupported value returns `400 unsupported_api_version`. Every response returns `API-Version`.
- `info.version` in openapi.json follows semantic versioning for the description itself.

## 2\. What is a breaking change

Breaking: removing an endpoint, field, tool or enum value; renaming one; changing a field's type or meaning; making an optional parameter required; changing an error `code`.

Not breaking, shipped without notice: new endpoints, new optional parameters, new response fields, new tools or resources, new error codes for new situations, changed prices and texts (they are data).

Clients should ignore fields they do not know.

## 3\. How deprecation is announced

- A deprecated endpoint keeps working for at least 6 months after the announcement.
- Its responses carry `Deprecation: @<unix-time>` (RFC 9745), `Sunset: <HTTP-date>` (RFC 8594) and `Link: <this page>; rel="deprecation"`.
- The operation is marked `deprecated: true` in openapi.json and listed below with its dates and replacement.
- For the MCP server, a deprecated tool says so in its description and is listed below; it is removed no earlier than its sunset date.
- After the sunset date the endpoint answers `410 Gone` with a JSON error that points to the replacement.

## 4\. Currently deprecated

Nothing is deprecated.

## 5\. Change log

- 2026-10-14: optional `API-Version` request header and `API-Version` response header; deprecation header support; this policy and the developer docs published.
- 2026-10-08: `/api/v1`, openapi.json and the MCP server published.

## lovefengis developer docs

- [Overview](https://lovefengis.com/gelistirici)
- [REST API reference](https://lovefengis.com/gelistirici/api)
- [MCP server](https://lovefengis.com/gelistirici/mcp)
- [CLI (npx lovefengis)](https://lovefengis.com/gelistirici/cli)
- [Sandbox (test environment)](https://lovefengis.com/gelistirici/sandbox)
- [OpenAPI 3.1 description (openapi.json)](https://lovefengis.com/openapi.json)
- [llms.txt agent guide](https://lovefengis.com/llms.txt)

Sorunuz kaldıysa kısa bir görüşme yeter.

15 dakikalık görüşme ücretsizdir ve sizi bağlamaz. İsterseniz kapsamla birlikte yazılı teklif iletiriz.

[Ücretsiz tanışma](https://lovefengis.com/gorusme) [hello@lovefengis.com](mailto:hello@lovefengis.com)

## Sitemap

See the full [sitemap](https://lovefengis.com/sitemap.md) for all pages on lovefengis.com.