> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/connectors/authentication/how-are-api-versioning-and-api-updates-handeled.md).

# How are API versioning and API updates handeled?

New API versions and updates of APIs.

Generally, we try to have the **latest version on APIs** e.g. /v4/  Once a /v5/ is released, with grace period of 60 days, and users want to use it immediately, they can overwrite the base-domain in the [ConnectorAuth](/connectors/authentication/setting-up-authentication.md).

If an old API version is still available and there is no immediate need, we will introduce a **new API version upon request** by customers with 48h notice by customers.

Next, we will inform all customers about the upgrade to /v5/ and any potential breaking changes. Additionally, we **ask customers to move their connectors to the new version**. Once we see there is either no negative interference or all customers upgraded, we change our primary connector version to /v5/ .

If a change only concerns individual endpoints, we either **inform customers and make the change immediately**, e.g. if the API just changed **without notice** and is unusable otherwise, or create a separate action with the new endpoint details and run both in parallel for some time, until all customer's flows are migrated.


---

# 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.locoia.com/connectors/authentication/how-are-api-versioning-and-api-updates-handeled.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.