# API Versioning Understanding and effectively managing versions is crucial to maximize benefits from APIs. Our API versioning system is primarily governed through the *'Accept'* HTTP header, which can be modified as required to access different versions. ### How to Use API Versioning When making a request to our API, specify the required API version in the 'Accept' HTTP header. Here is how you can do it: **Version 1 (Default Version)** If you want to use version 1, set your 'Accept' header to either 'application/json' or 'application/json;version=1'. Below are the examples: ```http Accept: application/json ``` or ```http Accept: application/json;version=1 ``` **Version 2 and Beyond** If you wish to use version 2 or any version beyond, indicate it in the 'Accept' header as 'application/json;version=2' for version 2, and so forth. Here is an example for version 2: ```http Accept: application/json;version=2 ``` ### Things to Remember * **Varied Endpoint Compatibility**: Please note that not all endpoints support multiple versions. Consequently, use your preferred version wisely. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.transactionlink.io/docs/v1/transactionlink-api/api-versioning.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.