> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-api-and-mcp/api/versioning-and-deprecation.md).

# Versioning and deprecation

The path version (`/v1`) changes only for incompatible changes to the operations it keeps; additive changes — new fields, new operations, new optional parameters — ship without a path change and bump this document's `info.version`. A deprecated operation is flagged `deprecated: true`, answers every request with a `Deprecation` header (RFC 9745, the date the replacement shipped) and a `Link` header pointing at the replacement's documentation, and keeps working until a removal date is announced as a `Sunset` header. No operation is deprecated today.

An operation can also be **withdrawn**: removed from this document and from the API, with its removal recorded on the changelog and the document's major version raised. Withdrawal is reserved for operations Delpha stops offering altogether, and it does not change the path version, because the operations that remain are unaffected.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.delpha.io/delpha-api-and-mcp/api/versioning-and-deprecation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.