# Deprecation & breaking changes policy

### Breaking changes

Breaking changes are only introduced in a new major contract version.

Example:

* `/v1.x/` → `/v2.0/`

Breaking changes include:

* Removing fields
* Renaming endpoints
* Changing response structures

### Deprecation notice

When an endpoint is scheduled for removal:

* Minimum notice period: 6 months
* Announcement via:
  * Release notes
  * Client email communication
  * GitBook deprecation notice

### Sunset policy

Deprecated versions remain supported for a minimum of 12 months unless regulatory constraints require earlier retirement.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://apentis.gitbook.io/apentis-api/release-notes/deprecation-and-breaking-changes-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.