> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/10.4/instance-administration/monitoring/api-deprecation.md).
# API deprecation
If you use custom plugins based on the plugin API or consume SonarQube Server 10.4 services, you should monitor the deprecation of the APIs.
{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.4 documentation. For a list of all 10.4 pages, see the [SonarQube Server 10.4 page index](https://2155789048-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL4urx4YsPFYDefLTrxao%2Fuploads%2FlBlJSWAzuhYo7WEorlJX%2Fsonarqube-server-10.4-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 10.4 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}
If you use custom plugins based on the [Plugin basics](/sonarqube-server/10.4/extension-guide/developing-a-plugin/plugin-basics.md) or consume SonarQube Server services through the [Web API](/sonarqube-server/10.4/extension-guide/web-api.md) then you will have to manage the possible API deprecations. See also the [Web API](/sonarqube-server/10.4/extension-guide/web-api.md) and the [Plugin basics](/sonarqube-server/10.4/extension-guide/developing-a-plugin/plugin-basics.md).
## Monitoring the deprecated Web API components
After an upgrade, you can check if an authenticated client of your SonarQube Server instance uses deprecated Web API endpoints and parameters in order to anticipate their drop. To do so, browse the deprecation log as illustrated below.
To download the deprecation log from the UI (with the **Administer System** permission):
1. In the top navigation bar of the SonarQube Server UI, select **Administration > System**.
2. In the top right corner of the **System Info** page, click **Download Logs > Deprecation Logs**.
{% hint style="info" %}
You can automate the retrieval of the deprecation log information by calling the Web API endpoint `api/system/logs` with `deprecation` as the value of the `name` parameter.
{% endhint %}
## Monitoring the deprecated Plugin API components
Check the [Plugin API release notes](https://github.com/SonarSource/sonar-plugin-api/releases) for deprecation notes.
---
# 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://docs.sonarsource.com/sonarqube-server/10.4/instance-administration/monitoring/api-deprecation.md?ask=&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.