I've been doing a lot of research at work with regards to Web API's and the proper way to design one to be consumed by other developers. While yes, smarter track could just change the serialization from xml soap to json, but this does not bring the web apis that already exist inline with modern evolvable web apis. Because all the web apis would still use POST only.
Modern Web APIs should use GET, PUT, POST, DELETE, etc, so I understand what the smarter tools staff was saying when they said its not that simple. But if they are going to put in the time to evolve the web services, stop calling them web services, they are web APIs. new namespace etc. no breaking changes for users who might be using servers v1, or services v2... /api/
I noticed MSFT Azure has a product called API Management, available for companies that want to expose their API to other developers. The Key point here is that the Azure API Management will transform or translate and old school web service into a modern web api. I am NOT suggesting SmarterTools do this, But If a user out there wants to spend the time to build an API inside of this feature in Azure, it sounds like it could be a decent work around. Till Smarter Tools gets the Web API out in a future version of SmarterTrack.