> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/api-documentation/api-change-policy.md).
# API Change Policy
This policy establishes a transparent and standardized process for removing API endpoints from the PlexTrac API while minimizing user disruption. By providing timely notification and support, we aim to facilitate a smooth transition for those who rely on these endpoints in their integrations with our platform.
PlexTrac values its customers and recognizes the importance of informing and assisting them with API endpoint removals. Their policy aims to minimize any negative impact and ensure a smooth transition.
## **Notification**
Before removing any API endpoint, provide at least 90 days' notice on the [API Change Log](/plextrac-documentation/api-documentation/api-change-policy/api-change-log.md) page. The notification will include the following:
* The release in which the API endpoint will be removed
* The endpoint being removed
* Replacement endpoint(s), when applicable
## **Removal Process**
Per the notification, the API endpoint will be eliminated from the codebase on the scheduled deployment date. PlexTrac will closely observe the effects of this action on their customers and will be ready to provide support in case any problems arise.
---
# 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.plextrac.com/plextrac-documentation/api-documentation/api-change-policy.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.
