So SambaPOS lets users configure just about everything including how it actually works. All of this can be done without editing any of the actual Code. Because of this power it has a fairly large learning curve to take advantage of the advanced capability.
We do have Configuration Tasks feature that would allow a developer to create dynamic configurations that can be fully automated and even stored on a global repository for easy access. You have full control on how configuration tasks work. So first you would need to solve the basic integration ideas with SambaPOS and your API then once you solve that you would look into the parts you want configurable and design a configuration task that asks the end user simple questions for configuration and then the task handles all the other stuff for the end user.
To get an idea of how a configuration task might work you can look at my Time Clock feature that I built and then built a configuration task to automate the install and management of the feature.
The development of the configuration task and even the PMS integration would not be simple or easy for the developer but once finished the end user would have a simple system that just works. That is what makes SambaPOS different… it doesnt rely on developers to develop specific features for specific businesses… it lets you do it. This frees up the actual SambaPOS developers to focus on new exciting features.