> For the complete documentation index, see [llms.txt](https://api.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api.dataloy.com/api-release-8.23/user-guides/enterprise-functionality/versioning.md). # Versioning **From**[ **version 2.10**](https://dataloy-cloud.atlassian.net/wiki/spaces/ARN/pages/923404364/Dataloy+API+2.10+Release+Notes) it is possible to have multiple versions of Dataloy API deployed on an application server. New API functionalities can be utilized for certain clients while at the same time continue to use older API versions for other clients. This usage of the system can remain until all clients are tested and working with the latest Dataloy API version. The API version is specified in the URL. **Latest Version** The latest version of Dataly API deployed at a customer's application server remains available at: | `http://[ip]:[port]/ws/rest` | | ---------------------------- | Older versions can be located at **ws/rest/version-number**. For example, if version 2.10.0 is deployed it will be found at: | `http://[ip]:[port]/ws/rest/6.38.0` | | ----------------------------------- | --- # 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://api.dataloy.com/api-release-8.23/user-guides/enterprise-functionality/versioning.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.