Buhahaha. We made special requests to the team from May through mid July - always a promise that new API documentation was coming, and yet it never arrived. I am so thankful to Andrea for pushing through our requests for help to the dev team, because coding against v16 proved taxing to our team, even though they had done a great job coding against v. 15.
We had to have our custom portal integration coded to a rather bizarre mixture of v1 API calls and with a bit of help from the SmarterTools dev team some "newer" API calls. That is so irritating as we KNOW that when the"new and improved" API is finally fixed - that is feature hardened and documented our code will probably break, and break badly which will require another month of changes to code against the "new and improved" API.
In addition, the ability to allow a user to log into their postmaster or other account from a third party app (such as our portal) was fundamentally broken in v. 16 - a HUGE issue for us. The answer? You must use the "same domain" on which SM resides. Seriously?! There are so many options to make this a secure from 3rd party applications, but no, just remove that feature altogether...
I assume... man I hate using that word... that SmarterTools is "actually" working on full API documentation, but for now, code against v1 API and you will have pretty good success.
Matthew J. Sine, General Manager8Dweb LLC"Making the Web a Happy Place"