Dear Trongate Developers, We're excited to announce some upcoming changes to the Trongate API Manager that will help bring it in line with current industry standards and best practices. However, we understand that these changes will involve breaking changes for many of you. We want to take this opportunity to explain these changes and how they will benefit you in the long run. One of the major changes we'll be making to the API Manager is the way parameters are declared and passed via the URL for making GET requests. Currently, the API Manager uses a custom syntax for declaring and passing parameters, which is not consistent with the widely-used industry standards such as RESTful API design. Therefore, we'll be updating the API Manager to follow the RESTful API standards and utilize query strings to pass parameters in GET requests. We understand that this change may require some modifications to your existing codebase, but we believe that this change will benefit you in the long run. By adhering to industry standards, the Trongate API Manager will become more interoperable with other systems and services, making it easier for you to integrate Trongate with other applications and services. This will ultimately save you time and effort in the long run. In addition to improving interoperability, following industry standards also means that your API endpoints will be more intuitive and easier to understand for other developers. As RESTful APIs are the most commonly used design pattern for APIs, this change will help you stay up-to-date with industry trends and make your APIs more familiar to other developers, making your codebase more accessible and easier to work with. We want to assure you that we're committed to making this transition as smooth as possible for you. We'll be providing detailed documentation and examples to help you understand the changes and make the necessary modifications to your codebase. Additionally, we'll be available to answer any questions you may have and help you with any issues you encounter during the transition. In conclusion, while we understand that these changes may require some adjustments to your existing codebase, we believe that they're necessary to bring the Trongate API Manager up-to-date with current industry standards. These changes will ultimately benefit you in the long run by making your codebase more interoperable, accessible, and future-proof. We're committed to making this transition as smooth as possible for you, and we look forward to seeing the benefits these changes will bring to your applications. For the vast majority of use cases, the changes that are coming up will not be breaking changes. We remain committed to the idea of making stability the highest priority for the Trongate framework. Thank you for being part of the Trongate community! Sincerely, The Trongate Team Photo by luis gomes: